Skip to content
MCP integration

Action security for MCP.

Evaluate tool calls before a host or gateway forwards them.

Get the package and source.

Connect the execution boundary.

Use the MCP host forwarding boundary or documented gateway. Only traffic routed through that boundary receives its policy decision.

An example to test

A remote tool request attempts to apply an unexpected patch. Evaluate the selected server, tool and final arguments before forwarding.

Illustrative workflow, not a customer deployment or a measured result.

Before connecting live policy

  1. Identify the handler that actually performs the side effect.
  2. Provide trusted identity, purpose and final action arguments.
  3. Configure the tenant’s assigned runtime and keep API credentials server-side.
  4. Test allowed, blocked and unavailable paths before production.

Integration example

Adapt this existing SDK pattern to your application. Names such as the agent, handler and session refer to your own objects. Follow the package documentation for compatible versions and complete setup.

Python 3.11+ is required for the Python SDK and local demo commands.

# Install MCP host / gateway support.
python -m pip install "agenticdome-python-sdk[mcp]"

from agenticdome_sdk.mcp_host import AgenticDomeMCPHostFirewall

firewall = AgenticDomeMCPHostFirewall()
result = await firewall.forward_with_firewall(
    mcp_request=request, context=context, forward_to_third_party=forward_to_mcp_server
)

agenticdome-demo --framework mcp --scenario remote_patch

Python demo commands evaluate fixed inputs against a bundled local policy; they do not instantiate the selected framework or prove a live integration. The TypeScript client and OpenClaw runtime plugin need their documented tenant configuration.

Prefer a gateway for service calls?

For compatible MCP, API, GraphQL and A2A requests, configure the assigned sidecar gateway without adding AgenticDome SDK hooks. Use the SDK path above for internal tools and richer framework context.

MCP schema validation and action policy work together.

The updated sidecar Gateway validates arguments against the server’s published inputSchema before forwarding. It obtains the caller’s accessible tool catalogue automatically and caches compiled validators locally.

The Python MCP host adapter can also validate schemas it captures from tool discovery; its strict schema option rejects missing or expired contracts. Existing SDK attachment points remain in place. A valid schema does not grant authority to execute the action.

Understand schema checks and approved contracts →

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.