Request path
Agent to MCP Boundary to policy and runtime check to downstream MCP server. The outcome is recorded after execution or blocked before downstream execution.
Documentation navigation
MCP Boundary docs
How MCP Boundary works
The local request path from agent to MCP Boundary to policy/runtime check to downstream server.
Still MCP
The agent still uses MCP. MCP Boundary sits between the agent and the downstream server and checks concrete tool calls before execution.
Dashboard role
The dashboard helps inspect setup, tools, policy, and activity. It is not a hosted remote gateway and does not become a separate approval authority.