Delete a webhook. Idempotent — succeeds even if already deleted.
AI agents call delete_mailbox_webhook to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Webhooks are system integrations that trigger external actions. Deleting a webhook removes configuration that cannot be easily recovered and stops critical integrations from functioning. While the operation is idempotent (safe to retry), the effect is permanently destructive. The blast radius is high if an agent deletes webhooks needed for production integrations, notifications, or critical workflows.
From the tool's definition Tool name explicitly states 'delete_mailbox_webhook' and description confirms it 'Delete a webhook'. This is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a webhook. Idempotent — succeeds even if already deleted. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for delete_mailbox_webhook: 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 Run402. Nothing to install.
delete_mailbox_webhook 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 delete_mailbox_webhook 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 delete_mailbox_webhook. 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.
delete_mailbox_webhook is provided by the Run402 MCP server (kychee-com/run402). 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 →