Critical Risk →

create_payment

Record a payment against an invoice

How to control create_payment ↓

What create_payment does on Mcp Ap2

AI agents use create_payment 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 create_payment needs a policy

This tool directly moves money or commits financial obligations by recording payments against invoices. Financial operations represent the most severe category and warrant critical severity due to potential for unauthorized fund transfers, fraud, or financial manipulation if misused by an AI agent.

From the tool's definition Tool name: 'create_payment'; Description: 'Record a payment against an invoice'. The server is explicitly described as 'Google's Agent-to-Agent Payment Protocol' handling payments and financial obligations.

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

How to control create_payment

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 create_payment:

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

Any call to create_payment 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 create_payment

What does the create_payment tool do? +

Record a payment against an invoice. 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 create_payment? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_payment: 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 create_payment? +

create_payment 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 create_payment? +

Yes. Add a rate_limit block to the create_payment 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 create_payment completely? +

Set action: deny in the PolicyLayer policy for create_payment. 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 create_payment? +

create_payment 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.