Permanently delete a webhook by ID. Returns the deleted webhook record.
AI agents call delete-webhook to permanently remove resources in Mcp Mailtrap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes webhook configurations. While not as critical as deleting user data or financial records, permanently removing webhooks can break integrations and event delivery pipelines that applications depend on. The permanent nature and inability to undo the operation places this firmly in the Destructive category rather than Write.
From the tool's definition Tool description states 'Permanently delete a webhook by ID' - the use of 'Permanently delete' explicitly indicates irreversible destruction of data.
Attacks that exploit this kind of access
Permanently delete a webhook by ID. Returns the deleted webhook record. It is categorised as a Destructive tool in the Mcp Mailtrap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for delete-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 Mcp Mailtrap. Nothing to install.
delete-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-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-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-webhook is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →