The deny the author says did not hold
An Apache local gateway whose readme says a deny is blocked, and whose author says one delete was not.
- Category
- Developer tools
- Who it is for
- Someone whose agent can already call MCP tools they did not mean to allow.
- Possible model
- Open source
- Difficulty
- Hard
- Inspired by
- Bastion · Bastion
- Original launch
- Watch the launch · Nov 5, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Nov 6, 2026. How we read a launch.
The startup idea
Soumil posted Bastion on November 5. His AI firewall told him three things that were not true. One of them let delete_thing on prod-db walk past a deny rule. Bastion is the open-source gateway he built between AI agents and their MCP tools. An adversarial review of his own code turned those findings up. The repository is SoumilBhandari/Bastion. The license is Apache 2.0. It sits between an agent, named as Claude Code, Cursor, or Claude Desktop, and the MCP servers it uses. It caps spend, rate-limits, enforces per-tool permissions, redacts or blocks arguments, and audits every call. One config file, one command, no cloud, no database. The readme says a denied call is blocked before it reaches the upstream and is recorded in the audit log. The post says a delete walked past a deny. The readme does not describe that miss. This page did not send a tool call, and it did not reproduce the bypass.
The opportunity is the log in front of the tool, for someone who will believe the audit over the slogan. A smaller product is one deny, one log line, and the author's miss quoted beside the rule. A gateway that claims the review found nothing is not this post.
Do not say the deny held if the author says it did not. Do not invent the other two false findings.
The problem
An agent can call a tool the policy meant to stop.
Who would pay for this?
- Primary
- Someone whose agent can already call MCP tools they did not mean to allow.
- Secondary
- A person who will read the audit log after a deny.
- Early adopter
- One config, one blocked call, the post's miss on the same page.
How could it make money?
Possible models. Nothing here is a claim about what Bastion charges.
- No price. Apache 2.0.
- No cloud and no database.
- The post does not name a seat.
What would the MVP look like?
- One config.
- A deny that is logged.
- No cloud.
- The author's bypass quoted, not smoothed over.
How to validate the idea
- Ask five people whether a denied delete reached the tool.
- If they say the readme proves it cannot, they did not read the post.
- Do not ship a rule you have not tried to walk past.
How to differentiate
- It is local.
- The audit is the product.
- The author published the miss.
- Do not become the agent.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Bastion did not write it.
- Product
- Bastion
- Source
- Bastion
- Film
- Bastion, the deny the author says failed
- Posted
- Nov 5, 2026 · 0:29
Product that inspired this idea
Soumil's post says his AI firewall told him three things that were not true. One of them let delete_thing on prod-db walk past a deny rule. Bastion is the open-source gateway he built between agents and their MCP tools. An adversarial review of his own code turned those up. The repository is SoumilBhandari/Bastion. The license is Apache 2.0. It is local-first: one config, one command, no cloud, no database. The readme says a denied call is blocked before it reaches the upstream and is written to the audit log. The post says a delete walked past a deny. The readme does not describe that miss. This page did not send a tool call.
Posted by @SoumilBhandari. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- security
Related startup ideas
- The fence Grok still walks through
An Apache check that stops a pasted key, except on Grok, where the send still goes.
- The scanner that never flies the agent
An Apache static scan of MCP tools, with a fix on the line and no execution.
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A visible team of agents in a world you can walk into
Use a shared world, not a log file, when several agents need a person to come over and decide.
- An Android remote for coding agents
A phone client for checking projects and steering agents when the laptop is closed.
- An inbox so the agents stay quiet
Collapse every coding-agent thread into one list, and only interrupt when one of them is stuck.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026