actiongate

Server Details

Paid MCP tools for ActionGate treasury safety endpoints.

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

3 tools

policy_gateInspect

Apply treasury policy to a proposed action and return allow, deny, or allow-with-limits. Paid via x402. Free tier: 5 calls/day per client.

ParametersJSON Schema

Name	Required	Description
`actor`	Yes	Actor metadata for the agent proposing the action.
`action`	Yes	Action payload to evaluate. Additional action-specific fields are accepted as passthrough.
`policy`	Yes	Policy pack input, including policy_id and any policy-specific override values.
`context`	No	Optional execution context such as chain state, balances, or treasury metadata.
`request_id`	No	Optional caller-supplied request identifier for tracing and receipts.

risk_scoreInspect

Score the risk of a proposed agent action before execution. Paid via x402. Free tier: 5 calls/day per client.

ParametersJSON Schema

Name	Required	Description
`actor`	Yes	Actor metadata for the agent proposing the action.
`action`	Yes	Action payload to evaluate. Additional action-specific fields are accepted as passthrough.
`context`	No	Optional execution context such as chain state, balances, or treasury metadata.
`request_id`	No	Optional caller-supplied request identifier for tracing and receipts.

simulateInspect

Estimate cost, failure risk, and notable side effects for a proposed action. Paid via x402. Free tier: 5 calls/day per client.

ParametersJSON Schema

Name	Required	Description
`actor`	Yes	Actor metadata for the agent proposing the action.
`action`	Yes	Action payload to evaluate. Additional action-specific fields are accepted as passthrough.
`context`	No	Optional execution context such as chain state, balances, or treasury metadata.
`request_id`	No	Optional caller-supplied request identifier for tracing and receipts.

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.