Critical Risk →

delete_payment

Delete a payment by ID

How to control delete_payment ↓

What delete_payment does on Mcp Ap2

AI agents call delete_payment to permanently remove resources in Mcp Ap2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_payment needs a policy

This tool irreversibly removes payment records from a financial system. Deletion of payments is a non-reversible action that affects financial integrity, audit trails, and accountability. Even in a protocol designed for authorization and audit (AP2), deleting payment records undermines the trust and audit guarantees the system is meant to provide.

From the tool's definition Tool name is 'delete_payment' and description states 'Delete a payment by ID'. The verb 'delete' is explicitly destructive, and payments are financial records that cannot be undone once removed.

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

How to control delete_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 delete_payment:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_payment"
  ]
}

delete_payment disappears from the agent's tool list entirely, and any attempt to call it is denied. 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_payment

What does the delete_payment tool do? +

Delete a payment by ID. It is categorised as a Destructive tool in the Mcp Ap2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_payment? +

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

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

Can I rate-limit delete_payment? +

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

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

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