send_agent_message
Send a message to a Rokha agent (default 'rokha-agent') and get its reply. With a logged-in identity (Authorization: Bearer <JWT>) the agent acts AS you — it can run your rigs (rig_run), read your saved keys/OAuth grants, and spend your budget; anonymous callers get general chat only. This is the...
This record as markdown: /tools/ai-rokha-rokha/send-agent-message.md
What send_agent_message does on Rokha
AI agents invoke send_agent_message to trigger actions in Rokha. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Message content to send to the agent |
agent_name | string | Yes | Name of the agent (e.g., 'rokha-agent', 'siren') |
Parameters from the server's own tool schema.
Why send_agent_message is rated High
Impersonates user to execute rigs, access secrets, and spend financial budget.
From the tool's definition agent acts AS you — run rigs, spend your budget
Attacks that exploit this kind of access
The rule that runs send_agent_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_agent_message, this is the rule to start with:
send_agent_message stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every send_agent_message call is checked against it from then on.
Questions about send_agent_message
Send a message to a Rokha agent (default 'rokha-agent') and get its reply. With a logged-in identity (Authorization: Bearer <JWT>) the agent acts AS you — it can run your rigs (rig_run), read your saved keys/OAuth grants, and spend your budget; anonymous callers get general chat only. This is the door to have Rokha do work on your behalf over MCP. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
send_agent_message accepts 2 parameters: message, agent_name. Required: message, agent_name. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for send_agent_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 Rokha. Nothing to install.
send_agent_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_agent_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_agent_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_agent_message is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
Across the catalogue