Critical Risk →

complete_checkout

Complete an ACP checkout by submitting a payment token. Finalizes the order with the seller. The checkout must be in

How to control complete_checkout ↓

What complete_checkout does on Mcp Ap2

AI agents use complete_checkout to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why complete_checkout needs a policy

This tool submits a payment token and finalizes an order, which constitutes committing a financial obligation. It is a payment completion action in a payment protocol (AP2), making it Financial category with critical severity due to the irreversible financial commitment and potential for misuse by an AI agent.

From the tool's definition Complete an ACP checkout by submitting a payment token. Finalizes the order with the seller.

Documented attack patterns abuse exactly the kind of access complete_checkout gives an agent:

How to control complete_checkout

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for complete_checkout:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_checkout": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to complete_checkout is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about complete_checkout

What does the complete_checkout tool do? +

Complete an ACP checkout by submitting a payment token. Finalizes the order with the seller. The checkout must be in. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on complete_checkout? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for complete_checkout: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Ap2. Nothing to install.

What risk level is complete_checkout? +

complete_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit complete_checkout? +

Yes. Add a rate_limit block to the complete_checkout rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block complete_checkout completely? +

Set action: deny in the PolicyLayer policy for complete_checkout. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides complete_checkout? +

complete_checkout is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.