Action Gateway connects agents to external services through an MCP URL with the tools, accounts, and permissions you choose.
Action Gateway Conceptspublic
Generated on 7 Nov 2026
Action Gateway connects applications and AI agents to tools through a managed MCP endpoint or SDK, with the accounts and permissions you choose. See What You Can Build for standalone agent examples.
Action Gateway endpoints provide MCP access to versioned tools and permissions for an actor.
An Action Gateway actor ID associates a user’s or workload’s connected accounts with its endpoints.
Action Gateway connections let tools use a specific account at a service such as GitHub, without exposing its credentials to the agent.
Action Gateway Toolbelts group tools into versioned collections for endpoint selection, group permissions, and preloading.
Action Gateway tool policies allow, require approval for, or deny calls within an endpoint version’s selected catalog.
Action Gateway preloading exposes known tools directly to the model while tool search discovers other relevant tools as needed.
Action Gateway tool search discovers relevant catalog tools and their schemas without loading the entire catalog into an agent’s context.
Action Gateway invokes named catalog tools with validated arguments and returns an outcome for each call.
Action Gateway runs an agent’s Python code in an ephemeral sandbox, with optional programmatic tool calling for advanced workflows.
Action Gateway uses bounded, tool-specific retries and provider idempotency where supported, without guaranteeing that arbitrary repeated calls are safe.