accept_dispute · Omise MCP Server MCP: Risk & Policy

WHAT IT DOES

What accept_dispute does on Omise MCP Server

AI agents use accept_dispute to commit financial operations through Omise MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why accept_dispute needs a policy

Accepting a dispute/chargeback is a financial action that concedes money back to the customer, directly resulting in a financial loss for the merchant. This is irreversible once processed and has direct monetary consequences, making it a Financial category tool with critical severity.

From the tool's definition Accept a dispute (accept the chargeback)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

accept_dispute Approval-gated

Any call to accept_dispute is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

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

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Omise MCP Server, so you can run agents against it safely.

FAQ

Questions about accept_dispute

What does the accept_dispute tool do? +

Accept a dispute (accept the chargeback). It is categorised as a Financial tool in the Omise MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on accept_dispute? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for accept_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 Omise MCP Server. Nothing to install.

What risk level is accept_dispute? +

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

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

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

accept_dispute is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.