update_dispute

Update a payment dispute with evidence

SERVERStripe SOURCE@modelcontextprotocol/server-stripe

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/stripe/update-dispute.md

WHAT IT DOES

What update_dispute does on Stripe

AI agents use update_dispute to create or update resources in Stripe, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stripe environment.

RISK

Why update_dispute is rated Medium

This tool modifies dispute data (a reversible Write operation) rather than deleting it or moving funds. However, updating dispute evidence can materially affect dispute outcomes and chargebacks, which may indirectly influence financial liability. The high severity reflects that misuse could alter dispute resolutions and potentially harm a business's chargeback metrics and Stripe account standing.

From the tool's definition Tool name is 'update_dispute' and description states 'Update a payment dispute with evidence' — this modifies an existing dispute record.

Risk signalsModifies dispute responses

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_dispute safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stripe, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_dispute, this is the rule to start with:

update_dispute Rate-limited

update_dispute stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_dispute": {
      "limits": [
        {
          "counter": "update_dispute_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stripe, apply this rule, and every update_dispute call is checked against it from then on.

FAQ

Questions about update_dispute

What does the update_dispute tool do? +

Update a payment dispute with evidence. It is categorised as a Write tool in the Stripe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_dispute? +

Register the Stripe MCP server in PolicyLayer and add a rule for update_dispute: 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 Stripe. Nothing to install.

What risk level is update_dispute? +

update_dispute is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_dispute? +

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

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

update_dispute is provided by the Stripe MCP server (@modelcontextprotocol/server-stripe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Stripe, and thousands of servers like it.

This server

All 27 Stripe tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →