Send a message to a specified platform (Telegram, WhatsApp, or Discord) via OpenClaw
AI agents use send_message to create or update resources in MCP OpenClaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP OpenClaw environment.
This tool creates new data (messages) on external communication platforms. While the action is reversible (messages can typically be deleted), it modifies external state and could be misused to spam, harass, or impersonate users across multiple platforms. The fact that it spans multiple platforms increases the potential blast radius.
From the tool's definition Tool description states it 'Send a message to a specified platform (Telegram, WhatsApp, or Discord)' - this creates new messages across external platforms, which is a reversible write operation.
Attacks that exploit this kind of access
Send a message to a specified platform (Telegram, WhatsApp, or Discord) via OpenClaw. It is categorised as a Write tool in the MCP OpenClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP OpenClaw MCP server in PolicyLayer and add a rule for send_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 MCP OpenClaw. Nothing to install.
send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_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 send_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.
send_message is provided by the MCP OpenClaw MCP server (starlink-awaken/mcp-openclaw). 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 →