Delete a webhook endpoint
AI agents call webhook_endpoint_destroy 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 a webhook endpoint, which cannot be undone. While not directly a financial transaction, it destroys configuration data that may be critical to payment processing workflows. In the context of a payment processing system (Omise), destroying a webhook endpoint could disrupt critical notification infrastructure, potentially causing payment events to be lost or unprocessed.
From the tool's definition Tool name contains 'destroy' and description states 'Delete a webhook endpoint'. This irreversibly removes a webhook endpoint configuration.
Attacks that exploit this kind of access
Delete a webhook endpoint. 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 webhook_endpoint_destroy: 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.
webhook_endpoint_destroy 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 webhook_endpoint_destroy 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 webhook_endpoint_destroy. 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.
webhook_endpoint_destroy 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 →