upload_dispute_document · Omise MCP Server MCP

WHAT IT DOES

What upload_dispute_document does on Omise MCP Server

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

WHY IT NEEDS A POLICY

Why upload_dispute_document needs a policy

This tool modifies dispute records by adding/uploading supporting documentation. While it involves financial payment disputes, it does not move money, create charges, or process refunds - it only adds evidence/attachments to an existing dispute. The Write category applies as it creates/modifies data reversibly.

From the tool's definition Tool description states 'Upload a document for a dispute' - this creates/uploads a new document object associated with a dispute record in the Omise payment system. The action is reversible (documents can typically be deleted or replaced).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_dispute_document Rate-limited

upload_dispute_document 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": {
    "upload_dispute_document": {
      "limits": [
        {
          "counter": "upload_dispute_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 upload_dispute_document

What does the upload_dispute_document tool do? +

Upload a document for a dispute. It is categorised as a Write tool in the Omise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_dispute_document? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for upload_dispute_document: 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 upload_dispute_document? +

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

Can I rate-limit upload_dispute_document? +

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

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

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