Action Gateway · Your assigned sidecar

One gateway for the calls your agents make.

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.

MCP toolsAPI requestsGraphQL operationsA2A messages
Plan your gateway connectionExplore with Abi
The connection in plain terms

Your application.
One policy boundary.

  • 01 · Your applicationSupplies the existing service URL, native request and caller identity.
  • 02 · AgenticDome sidecar gatewayVerifies identity and evaluates the requested action against your policy.
  • 03 · Your serviceReceives the request when policy permits forwarding.

Your security team defines the boundary. Your developers configure the connection.

Configure once. Use existing destinations.

A clear handoff between security and development.

01 · SECURITY / AI TEAM

Set the organisation boundary

Choose permitted destination domains and trusted caller identities. Use an existing identity provider or approve an AgenticDome-managed deployment.

02 · DEVELOPMENT TEAM

Use your assigned connection

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.

03 · OPERATIONS TEAM

Review decisions and coverage

Test permitted and denied actions. Review recorded policy decisions, available outcomes and runtime health in the same workspace.

Different protocols. Shared identity and policy.

MCP

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.

Explore MCP action security →

API

Supply your target API URL, HTTP method and request content. Evaluate the destination and proposed action before an allowed request reaches the business system.

GraphQL over HTTP

Route JSON-over-HTTP GraphQL requests through the gateway so operation type, selected fields and variables can inform action policy.

A2A

Carry caller identity and available delegation context with agent-to-agent requests. Apply recipient and action boundaries to participating workflows.

Explore delegated authority →
Keep the framework you chose

Use native clients, including Docker Agent and AWS Strands.

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.

Compare connection pathsRead the gateway quickstart
Meet Abi

Your AI deployment concierge.

Describe your environment and what you want to protect. Abi helps compare connection options and prepare a deployment blueprint for your team to review.

Explore Abi

Start with the workflow that matters.

Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.

Try the local demo Book a deployment review Meet Abi