Send a message through a connected OpenClaw messaging channel (Slack, Discord, Telegram, etc.)
AI agents use send_message to create or update resources in ClawDaemon MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClawDaemon MCP environment.
This tool creates or posts data to external messaging platforms without permanently destroying information or moving financial assets. While it has social/reputational implications if misused (spam, impersonation, harassment across 23+ platforms via the daemon), the action itself is reversible and does not irrevocably modify or delete data.
From the tool's definition Tool is called 'send_message' and described as 'Send a message through a connected OpenClaw messaging channel (Slack, Discord, Telegram, etc.)' — this creates new data (a message) in an external system that is reversible (messages can be edited or deleted…
Attacks that exploit this kind of access
Send a message through a connected OpenClaw messaging channel (Slack, Discord, Telegram, etc.). It is categorised as a Write tool in the ClawDaemon MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClawDaemon 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 ClawDaemon MCP. 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 ClawDaemon MCP server (mordiaky/clawdaemon-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 →