Critical Risk →

accept_dispute_claim

Accept liability for a dispute claim via POST /v1/customer/disputes/{id}/accept-claim. The disputed amount is refunded to the buyer. Terminal action.

How to control accept_dispute_claim ↓

What accept_dispute_claim does on Mcp Ap2

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

This tool triggers a financial refund to a buyer by accepting liability for a dispute claim. It is explicitly described as a terminal (irreversible) action with direct monetary consequences, making it Financial and critical severity.

From the tool's definition 'Accept liability for a dispute claim', 'The disputed amount is refunded to the buyer', 'Terminal action'

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

How to control accept_dispute_claim

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

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

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

What does the accept_dispute_claim tool do? +

Accept liability for a dispute claim via POST /v1/customer/disputes/{id}/accept-claim. The disputed amount is refunded to the buyer. Terminal action. 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 accept_dispute_claim? +

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

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

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

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

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