Delete a transfer (only for pending transfers)
AI agents call destroy_transfer 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 irreversibly deletes a transfer object. While restricted to pending transfers, deletion of financial records is a destructive operation with high blast radius — misuse could remove pending payment transfers, disrupting fund flows and audit trails. Destructive ranks above Financial here because the action is a data deletion rather than a direct movement of funds.
From the tool's definition 'Delete a transfer' and tool name 'destroy_transfer' — explicitly deletes a financial transfer record
Attacks that exploit this kind of access
Delete a transfer (only for pending transfers). 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_transfer: 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_transfer 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_transfer 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_transfer. 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_transfer 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 →