Show HN: mcp-gate – Ephemeral capability token proxy for LLM tool execution in Go
I built mcp-gate , a small Go reverse proxy for a problem I keep coming back to with LLM agents: How much authority should we actually give a model when it calls a tool? Repo: https://github.com/ananthaprakashb/mcp-gate A typical agent integration eventually ends up holding something powerful: an API key, service credential, OAuth token, or access to an MCP/tool server that can perform multiple operations. Even when the model is supposed to perform one very specific action, the credential it indirectly controls may authorize far more. I wanted the authorization boundary to look more like this: The model never receives the upstream API credential. Instead, the trusted orchestrator exchanges its gate credential for an ephemeral capability token authorizing one specific operation. For example: { "route": "tickets", "method": "POST", "path": "/v1/tickets", "ttl_seconds": 15 } The returned bearer token is HMAC-s...
Comments
Post a Comment