Delete a registered webhook by its ID.
AI agents call delete_webhook to permanently remove resources in Postcardbot — 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, which cannot be easily recovered. Misuse could disable critical notification infrastructure, break integrations, or disrupt monitoring of postcard delivery events. While not as severe as deleting financial records or postcards themselves, it is destructive in nature and warrants high severity due to potential operational impact.
From the tool's definition Tool name explicitly states 'delete_webhook' and description confirms 'Delete a registered webhook by its ID.' The verb 'delete' combined with 'by its ID' indicates irreversible removal of a configured resource.
Attacks that exploit this kind of access
Delete a registered webhook by its ID. It is categorised as a Destructive tool in the Postcardbot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postcardbot 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 Postcardbot. 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 Postcardbot MCP server (postcardbot/mcp-server). 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 →