Critical Risk →

refund_payment

Refund a captured payment (full or partial).

How to control refund_payment ↓

What refund_payment does on Mcp Ap2

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

Refunds constitute direct financial transactions that commit monetary obligations and reverse captured payments. This is a core Financial category action. Combined with the AP2 context (Agent-to-Agent Payment Protocol), misuse could result in unauthorized refunds, financial loss, and fraud.

From the tool's definition Tool name 'refund_payment' and description 'Refund a captured payment (full or partial)' explicitly perform a financial operation that moves money back to a customer or account.

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

How to control refund_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 refund_payment:

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

Any call to refund_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 refund_payment

What does the refund_payment tool do? +

Refund a captured payment (full or partial). 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 refund_payment? +

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

refund_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 refund_payment? +

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

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

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