messages_edit

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/messages-edit.md

WHAT IT DOES

What messages_edit does on Dialogbrain

AI agents use messages_edit to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.

Parameter	Type	Required	Description
`new_text`	string	Yes	Replacement text for the message.
`thread_id`	string	Yes	Thread ID containing the message (numeric DB id or channel_ref like 'telegram:-100123').
`message_id`	string	Yes	ID of the message to edit (from messages.read_history).

Parameters from the server's own tool schema.

RISK

Why messages_edit is rated Medium

messages_edit modifies content (message text) that has already been created. This falls under Write category (reversible modification). Severity is medium because: (1) the edits are limited to the user's own messages by platform constraints, (2) the modification is reversible (can be edited again), and (3) blast radius is constrained by channel-specific time windows (48h Telegram, 15min WhatsApp).

From the tool's definition Tool description explicitly states 'Edit the text of a message you already sent, in place' and 'supported on Telegram, WhatsApp, LiveChat' — this is a reversible modification of existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs messages_edit 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_edit, this is the rule to start with:

messages_edit Rate-limited

messages_edit stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "messages_edit": {
      "limits": [
        {
          "counter": "messages_edit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every messages_edit call is checked against it from then on.

FAQ

Questions about messages_edit

What does the messages_edit tool do? +

Edit the text of a message you already sent, in place. Supported on Telegram, WhatsApp, LiveChat, Max.ru, LINE, WeChat and similar channels; NOT supported on Gmail, Instagram, or LinkedIn (their platforms forbid editing) — those return an explicit error. Note: channels impose their own limits (own messages only, edit time windows such as ~48h on Telegram / ~15min on WhatsApp). Get the message_id from messages.read_history (each row's id). It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does messages_edit accept? +

messages_edit accepts 3 parameters: new_text, thread_id, message_id. Required: new_text, thread_id, message_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on messages_edit? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for messages_edit: 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.

What risk level is messages_edit? +

messages_edit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit messages_edit? +

Yes. Add a rate_limit block to the messages_edit 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.

How do I block messages_edit completely? +

Set action: deny in the PolicyLayer policy for messages_edit. 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.

What MCP server provides messages_edit? +

messages_edit 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.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →