messages_forward

Forward a message from one thread to another. Supports native Telegram forwarding (preserves original sender attribution) and text-based forwarding for cross-channel scenarios.

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

Medium RISK CLASS

Category Write

Parameters 42 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-forward.md

WHAT IT DOES

What messages_forward does on Dialogbrain

AI agents use messages_forward 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
`dest_thread_id`	string	—	Destination thread to forward into. Provide at least one of dest_thread_id or recipient_name. To forward into the active conversation, pass the current thread_i
`recipient_name`	string	—	Name of person to forward to (channel auto-resolved). Provide at least one of dest_thread_id or recipient_name. Use only when forwarding to a different contact
`source_thread_id`	string	Yes	Thread containing the message to forward (e.g., 'telegram:123456' or numeric DB ID)
`source_message_id`	string	Yes	ID of the message to forward

Parameters from the server's own tool schema.

RISK

Why messages_forward is rated Medium

Forwarding messages is a write operation that creates new data (copies of messages in new locations) and modifies conversation threads. It does not delete, execute code, or move money, so Write is the appropriate category.

From the tool's definition Tool description states 'Forward a message from one thread to another' with explicit support for Telegram and cross-channel forwarding. This action creates new message copies in destination threads, modifying the state of those conversations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

messages_forward Rate-limited

messages_forward 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_forward": {
      "limits": [
        {
          "counter": "messages_forward_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_forward call is checked against it from then on.

FAQ

Questions about messages_forward

What does the messages_forward tool do? +

Forward a message from one thread to another. Supports native Telegram forwarding (preserves original sender attribution) and text-based forwarding for cross-channel scenarios. 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_forward accept? +

messages_forward accepts 4 parameters: dest_thread_id, recipient_name, source_thread_id, source_message_id. Required: source_thread_id, source_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_forward? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for messages_forward: 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_forward? +

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

Can I rate-limit messages_forward? +

Yes. Add a rate_limit block to the messages_forward 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_forward completely? +

Set action: deny in the PolicyLayer policy for messages_forward. 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_forward? +

messages_forward 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

forward-email on Meme MCP Server → The MCP Attack Database →

Guides

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