Managing MCP tool permissions: an Agent Proxy for pre-authorization per tool
radim11 · reddit · 2026-09-07
A Reddit thread on permission control when agents use MCP servers. The author's team built an Agent Proxy that:
- Keeps API keys outside the agent context
- Restricts which hosts, methods, and paths the agent can access
- Allows/denies individual MCP tools, exposing only selected ones
- Runs the same policy with agents like Codex
- Keeps an audit trail of proxied requests
For example, an agent connecting to Linear can be limited to specific tools instead of the full MCP toolset. The question posed: do you approve tool calls as they happen, or control tool exposure upfront?
More from coding & agent
- Resin lets an agent build standalone LLM inference engines; vLLM and SGLang optimize DeepSeek kernels differently — AccBalanced · 2026-10-27
- Alchemy adds effect/Workflow support across Durable Objects, Workflows and Lambda Durable Functions — samgoodwin89 · 2026-10-27
- Alchemy's Lambda Web Functions run plain Node web servers on Lambda, no OpenNext needed — samgoodwin89 · 2026-10-27
- Alchemy Domain brings domain-driven design and story testing to Effect backends — samgoodwin89 · 2026-10-27
- Alchemy makes all ~2,850 AWS bindings work from any cloud, not just S3/Lambda/DynamoDB — samgoodwin89 · 2026-10-27
- Production AI agent scored 95% robustness at baseline, 37% under adversarial attack — njyx · 2026-10-27