Delete a dispute document
AI agents call destroy_dispute_document to permanently remove resources in Omise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes dispute documentation, which cannot be undone. Dispute documents are critical financial and legal records in payment processing. Unauthorized or accidental deletion could destroy evidence, violate regulatory compliance requirements (PCI-DSS, chargeback documentation), and expose the business to legal liability.
From the tool's definition Tool name is 'destroy_dispute_document' with description 'Delete a dispute document'. The verb 'destroy' and 'delete' explicitly indicate irreversible removal of data.
Attacks that exploit this kind of access
Delete a dispute document. It is categorised as a Destructive tool in the Omise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for destroy_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.
destroy_dispute_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the destroy_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.
Set action: deny in the PolicyLayer policy for destroy_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.
destroy_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →