messages_delete
Delete a message from a thread. Supports Telegram, WhatsApp, and other connected channels. Note: Some channels have time limits on message deletion.
This record as markdown: /tools/io-github-saloprj-dialogbrain/messages-delete.md
What messages_delete does on Dialogbrain
AI agents call messages_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
thread_id | string | Yes | Thread/channel ID containing the message |
message_id | string | Yes | ID of the message to delete |
Parameters from the server's own tool schema.
Why messages_delete is rated Critical
Deletion of messages is an irreversible operation that cannot be undone, fitting the Destructive category. Although some channels may have time limits restricting deletion windows, the core function removes data permanently.
From the tool's definition Tool name is 'messages_delete' and description states 'Delete a message from a thread.' The verb 'delete' combined with the explicit action of removing messages indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs messages_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For messages_delete, this is the rule to start with:
messages_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every messages_delete call is checked against it from then on.
Questions about messages_delete
Delete a message from a thread. Supports Telegram, WhatsApp, and other connected channels. Note: Some channels have time limits on message deletion. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
messages_delete accepts 2 parameters: thread_id, message_id. Required: thread_id, message_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for messages_delete: 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 Dialogbrain. Nothing to install.
messages_delete 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 messages_delete 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 messages_delete. 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.
messages_delete is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue