Deleta um webhook existente para uma sessão na Zappaz API
AI agents call delete_webhook to permanently remove resources in Zappaz MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes webhook configurations, which cannot be undone without manual reconfiguration. Deletion of webhooks is an irreversible destructive action. While not as severe as deleting messages or groups directly, it represents permanent removal of infrastructure configuration.
From the tool's definition The tool name is 'delete_webhook' and the description states 'Deleta um webhook existente para uma sessão na Zappaz API' (Delete an existing webhook for a session in the Zappaz API).
Attacks that exploit this kind of access
Deleta um webhook existente para uma sessão na Zappaz API. It is categorised as a Destructive tool in the Zappaz MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zappaz MCP Server 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 Zappaz MCP Server. 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 Zappaz MCP Server MCP server (viiniolliveira/zappaz-mcp). 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 →