messages_send
Send a message back through the same OpenClaw conversation route.
This record as markdown: /tools/openclaw/messages-send.md
What messages_send does on OpenClaw
AI agents use messages_send to create or update resources in OpenClaw, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenClaw environment.
Why messages_send is rated Medium
This tool writes/creates data (a message) and transmits it, which is reversible and has side effects limited to communication within a conversation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve data (Read).
From the tool's definition Tool name 'messages_send' and description 'Send a message back through the same OpenClaw conversation route' indicate the tool creates and transmits a message within an existing conversation context.
Attacks that exploit this kind of access
The rule that runs messages_send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For messages_send, this is the rule to start with:
messages_send 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.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every messages_send call is checked against it from then on.
Questions about messages_send
Send a message back through the same OpenClaw conversation route. It is categorised as a Write tool in the OpenClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenClaw MCP server in PolicyLayer and add a rule for messages_send: 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 OpenClaw. Nothing to install.
messages_send 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 messages_send 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_send. 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_send is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue