Deleta uma mensagem atraves da Zappaz API
AI agents call delete_message 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.
Deleting messages is a destructive action that cannot be undone. Once a message is deleted via the WhatsApp API, it is permanently removed and cannot be recovered. In the context of an automated agent, misuse could result in loss of important communications, conversation history, or evidence. The high severity reflects the potential for significant data loss and the irreversible nature of the operation.
From the tool's definition Tool name is 'delete_message' and description states 'Deleta uma mensagem' (Portuguese: 'Deletes a message'). This is an irreversible deletion operation.
Attacks that exploit this kind of access
Deleta uma mensagem atraves da 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_message: 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_message 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_message 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_message. 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_message 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 →