Delete a bot message by ID
AI agents call delete_message to permanently remove resources in Solafon MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a message) and cannot be undone. Deletion operations are irreversible, making this a Destructive category tool. While the blast radius is limited to a single message rather than critical system data, unauthorized deletion of conversation history could still cause significant harm by destroying audit trails, evidence, or important communication records.
From the tool's definition delete_message - Delete a bot message by ID. The verb 'delete' combined with the operation of removing a message by ID indicates irreversible data removal.
Attacks that exploit this kind of access
Delete a bot message by ID. It is categorised as a Destructive tool in the Solafon MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Solafon 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 Solafon MCP. 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 Solafon MCP server (solafon/solafon-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 →