Action Control

Action Gateway (MCP)

Give an agent its business actions as MCP tools through the managed Action Gateway, with an agent key.

The Action Gateway is a managed MCP endpoint for your agents’ business actions. Each action the agent may run becomes a tool, whether or not protection is on yet; every tool call goes through the same pipeline as integrity.execute. Agents need no SDK and no code change beyond their MCP configuration.

Before a person turns on protection for a connector that can run the action, a call with a real id executes nothing and returns an error with turn_on_protection_url, the page where an admin turns it on. Test ids (ch_test_refundable, …) run through the Test connector right away: simulated, no money moves.

Action Gateway endpoint

https://audon.ai/mcp/actions

Before: agent → payment API. After: agent → Action Gateway → payment API.

Authentication

Agent keys: Authorization: Bearer aa_agent_…. The key decides which agent is calling and which tools it sees. Create the key under Agents in the app (see the quickstart), or let the agent register itself: with an enrollment key (aa_enroll_…) the gateway offers only register_agent, which returns the agent’s own key. See For agents. Any other credential (an API key, an OAuth token) gets 401 or 403.

Configure your agent

Pick your client. Signed in, the agent’s page shows the same snippets with its key filled in.

curl -X POST https://audon.ai/v1/integrity/actions \
  -H "Authorization: Bearer $AUDON_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: first-test-$(date +%s)" \
  -d '{"action_type":"refund.create","resource":"ch_test_refundable","amount_minor":100,"currency":"USD"}'

Tools

Tool	Action
`refund_create`	`refund.create`
`credit_create`	`credit.create`
`discount_create`	`discount.create`
`subscription_cancel`	`subscription.cancel`
`subscription_update`	`subscription.update`
`order_cancel`	`order.cancel` (Shopify or Webhook connector)
`email_send`, `crm_contact_delete`, …	Your organization’s own action types (catalog and custom), dots become underscores
`report_outcome`	Report the outcome of a decision-only action you executed
`agent_status`, `request_actions`, `send_test_action`, `list_actions`	Your status, asking a person for more actions, a simulated test action, what you could ask for
`action_status`	The current decision and outcome of one of this agent’s actions
`action_retry`	The next attempt, only when `retry_safe`

An agent sees the tools of its allowed actions only (and those it may test before approval). Each action tool takes the same fields as the API (resource, amount_minor, currency, idempotency_key, params, …). The result carries the decision, the reason, the outcome and what to do next.

Security prerequisite: remove the direct path

Tools must actually run through the gateway. Remove the agent’s own credentials for the same systems (for example a Stripe secret key in its tool configuration), or it can bypass the controls. The gateway and every connector response repeat this note.

Action Gateway and the Audon MCP server

Action Gateway (/mcp/actions): agents execute business actions, with agent keys.
Audon MCP server (/mcp): people’s agents use the Audon product itself (audits, findings, policies), with OAuth. See MCP server.

Last updated 2 November 2026