Set the organisation boundary
Choose permitted destination domains and trusted caller identities. Use an existing identity provider or approve an AgenticDome-managed deployment.
Govern MCP, API, GraphQL and A2A calls through your assigned sidecar gateway. Keep your existing services and use compatible native clients without adding AgenticDome SDK hooks.
Your security team defines the boundary. Your developers configure the connection.
Choose permitted destination domains and trusted caller identities. Use an existing identity provider or approve an AgenticDome-managed deployment.
Copy your sidecar gateway URL and Runtime key from your account. Supply the existing target service URL and appropriate identity with requests. Individual destination registration is not required.
Test permitted and denied actions. Review recorded policy decisions, available outcomes and runtime health in the same workspace.
Keep the MCP client's protocol messages intact. For a tool call, the client supplies the tool name and arguments; the gateway supplies the policy boundary and records its decision. The updated Gateway validates arguments against the server’s published input schema before forwarding.
Explore MCP action security →Supply your target API URL, HTTP method and request content. Evaluate the destination and proposed action before an allowed request reaches the business system.
Route JSON-over-HTTP GraphQL requests through the gateway so operation type, selected fields and variables can inform action policy.
Carry caller identity and available delegation context with agent-to-agent requests. Apply recipient and action boundaries to participating workflows.
Explore delegated authority →Choose the gateway when your application can configure its service connection and you want protection without installing an AgenticDome framework adapter. Customer onboarding provides native client examples for Docker Agent, AWS Strands, CrewAI and LangGraph.
Calls routed through the gateway receive its checks. Internal tools and local execution can use SDK hooks for additional context and control. For Docker Agent, add its mandatory native guard through deployment configuration to check local tools without changing application code.
Describe your environment and what you want to protect. Abi helps compare Gateway, Docker native guard and SDK options, explain identity and MCP schema checks, and prepare a deployment blueprint for your team to review.
The MCP server publishes inputSchema: the required fields, types and allowed structure of each tool’s arguments. Your client keeps its native tool-call message.
AgenticDome obtains the catalogue using the same caller’s server access and checks arguments before forwarding. Compiled schemas are cached locally, so warm calls do not fetch a catalogue each time.
A correctly shaped request still needs the right identity, purpose and authority. Review schema changes in Discovery; optionally pin a sensitive tool’s approved input contract in Tool & MCP Registry.
Example: a customer lookup expects a text customer ID. A numeric ID fails validation before forwarding. A valid lookup still passes through your action policy. No schema upload or per-tool audience setup is needed.
Send MCP, API, GraphQL and A2A requests through your sidecar Gateway. Keep existing service URLs and native clients. This network pathway requires no AgenticDome SDK hooks in your application.
Add Docker Agent’s mandatory tool_guard integration for shell, file and local-tool proposals. The adapter asks your sidecar for an allow-or-deny decision before execution, including auto-approved calls.
hooks.d configuration. Load approved identity settings through your secret manager.With the native guard installed, a denial or missing valid decision stops the proposal. Docker executes an allowed tool under its own permissions. The guard records a pre-execution policy decision. Retain Docker’s sandbox and access controls, and review that decision alongside action and outcome evidence.
Use an updated sidecar and a compatible Docker Agent runtime with the installed guard adapter. Your application code stays the same; SDK hooks remain available for richer framework context and other execution boundaries.
Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.