Show HN: AgentPort – Open-source Security Gateway For Agents

Show HN (score: 5)
Found: April 29, 2026
ID: 4401

Description

Other
Show HN: AgentPort – Open-source Security Gateway For Agents Hey HN!

I've been wanting to use something like OpenClaw for a while but couldn't get myself to give it access to anything important due to all the risks involved. Prompt injection is still a problem (even though some people seem to ignore it) and so are hallucinations and mishaps that cause agents to do things like delete production data [1].

Even harnesses like Claude Code and Codex are subject to this, particularly since we're getting progressively looser about how we run them e.g. Conductor is really popular and runs agents without any sandboxing.

That means we're in a bit of an all-or-nothing situation. There are people who just ignore the risks and connect everything to their agents and reap benefits from it while being subject to more risk, and there are others that just don't connect anything because they are mindful of the potential issues.

I've been quite cautious but have wanted to run more autonomous agents and so I built the component I needed to enable me to do so: AgentPort.

AgentPort is a gateway that connects to any service (e.g. Gmail, GitHub, Stripe, PostHog, Linear) and let's you set granular permissions for what the agent can do automatically, what it needs your approval for, and what it can never do.

For example, you can set `list_customers` and `get_customer` on the Stripe integration to "Auto-approve" but `create_refund` to "Ask for approval". The agent will thus be able to do a lot in the background independently but when it comes to a potentially destructive operation it will be blocked and receive an approval link to send to you. You can then approve or deny the call with those exact parameters e.g. `create_refund(customer_id: 1234, amount: 12)`.

Agents connect via MCP or CLI and have access to all the integrations you connected without ever getting API keys. Kind of like Composio but with granular permissions and open source.

The goal with AgentPort is to specifically address two vulnerabilities that agents are subject to:

1. Destructive operations on downstream services: It can't delete a database unless you explicitly approve 2. Credential exfiltration: Your agent never sees API keys

AgentPort also helps with sensitive data exfiltration, but that is more nuanced and complicated to defend against if the agent has an internet connection [2].

Ultimately, AgentPort was the missing piece for me to start running more autonomous agents that have access to third-party services, and hopefully it can unlock use cases for you too. There's a ton more work needed around securing agents (Claws in particular) and I've both been writing about it [3] and intend to do more in this space, so if you're thinking about similar things let's have a chat.

The repo is https://github.com/yakkomajuri/agentport and you can run it locally with docker compose in a minute or use the one-liner install to deploy a prod instance (domain, TLS, etc.) in just a few mins as well.

[1] "An AI agent deleted our production database. The agent's confession is below" (https://news.ycombinator.com/item?id=47911524)

[2] See my post "On agents dropping production databases": https://yakko.dev/blog/on-agents-dropping-production-dbs

[3] https://yakko.dev/blog

More from Show

Show HN: ValuePair – a friendship app that cares about values first

Show HN: ValuePair – a friendship app that cares about values first Hey,<p>I would like to show you my project, but it&#x27;s difficult because it only works with a registration, so I explain the concept to you.<p>The Idea: Everyone who registers has to do an onboarding and answer meaningful questions that help you to find a right match. The matching happens by the system. Once you&#x27;re done with the onboarding, you enter the pool. When a match is found, you go into a 1on1 14 question-set with that person. All answers are revealed immediately. At the end both decide if they form a connection or not. Only if both agree, the chat opens. Once a connection is formed, they can play through other prepared question sets, so the conversation doesn&#x27;t get dry. It&#x27;s also possible to create custom question sets to play through with your connected matches.<p>I just got this idea because I really wanted away from all the typical friendship and dating apps that are just a marketplace of user profiles. I feel like that&#x27;s the only hook other apps offer, people come back because they are bored and browse through profiles. On tinder it&#x27;s swiping through pictures and on other apps it&#x27;s a list of profiles where you can filter with your matching criteria. But all that felt just shallow to me. I think people rarely ask the right questions each other, like really mandatory things that matter to form a any kind of relationship with someone. I&#x27;ve been on multiple different social platforms and it always felt mega shallow. Most people can&#x27;t even start a good conversation, it&#x27;s often just stuck at small talk. Maybe it&#x27;s not even peoples fault, that&#x27;s why I tried with these question sets to tackle multiple problems. First, that you don&#x27;t even have to bother with someone if you have entirely different worldviews, which you would normally just find out if you talk long enough with someone. And second, just killing the small talk issue, by giving people a base.<p>So before I started coding this project, I actually did a research if there is anything backed by science to find out, which kind of questions would actually matter to find out, if you can handle someone. There were a lot of studies I&#x27;ve found e.g. &quot;Aron and colleagues (1997)&quot;, &quot;Hall (2019)&quot;, &quot;Byrne (1971)&quot;, &quot;Finkel and colleagues (2012)&quot; and &quot;Hazan and Shaver (1987)&quot;. I took their research work and tried to create questions based on them.<p>The project is running on Next, Postgresql, everything dockerized, running on a small Hetzner VPS. I used Claude+Codex to develop everything, but I wouldn&#x27;t say it&#x27;s really vibecoded, since I work as a Senior Dev and I used my main tech stack.<p>It&#x27;s an open beta currently and it&#x27;s live for like 14 days - I have ~150 users right now. And honestly, I am really overwhelmed by those numbers, because it&#x27;s the first time that I ever managed to attract this amount of people on a project I&#x27;ve launched.<p>When I started, I launched it as a closed beta, so it was invite only. During that period I got so much good feedback from people, it was incredible. I implemented almost everything my first users told me. Since all the changes, I didn&#x27;t retrieve any further feedback what people wish would be different. It&#x27;s just constant good feedback since then. People contact me from alone and just tell me how much they like these questions and the loop.<p>My marketing strategy is mainly Reddit currently, but I started also new methods. I found some super relevant subreddits that had no rules against advertising. When I wrote my posts on reddit, I didn&#x27;t mention a product name or link. I&#x27;ve only described the idea and if somebody would have interest trying it out. That worked surprisingly well. Another thing I&#x27;ve done was using a social app that allows anonymous posts at your current location, kinda something like &quot;Nextdoor&quot;. Posts on this app bring me daily 1-5 new registrations.<p>I wonder what you guys think about it and I am open for any critics!

No other tools from this source yet.