Delete a recipient
AI agents call destroy_recipient 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 deletes recipient records from the Omise payment system. Deletion is irreversible and cannot be undone, fitting the Destructive category. Severity is high because unintended deletion of recipient records could disrupt payment operations, affect financial workflows, and potentially impact multiple dependent transactions or scheduled payments.
From the tool's definition Tool name is 'destroy_recipient' with description 'Delete a recipient'. The verb 'destroy' combined with 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a recipient. 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_recipient: 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_recipient 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_recipient 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_recipient. 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_recipient 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 →