Critical Risk →

disable_stored_payment_method

Delete a stored payment method (shopper opt-out).

How to control disable_stored_payment_method ↓

What disable_stored_payment_method does on Mcp Ap2

AI agents call disable_stored_payment_method 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 disable_stored_payment_method needs a policy

The tool deletes a stored payment method, which is an irreversible action (destruction of stored data). While framed as a shopper opt-out, removing a payment method cannot be undone without re-adding it, making this Destructive.

From the tool's definition 'Delete a stored payment method' — explicitly deletes a stored financial credential/payment method irreversibly

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

How to control disable_stored_payment_method

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

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

disable_stored_payment_method 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 disable_stored_payment_method

What does the disable_stored_payment_method tool do? +

Delete a stored payment method (shopper opt-out). 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 disable_stored_payment_method? +

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

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

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

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

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