AI agents invoke send to trigger actions in Opencode. 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.
This tool sends messages to remote coding environments (OpenCode instances) via SSH reverse tunnels, triggering execution of coding tasks or operations on remote machines. The effects depend on the message content — an AI agent could instruct the remote coding environment to run arbitrary code, modify files, execute shell commands, etc.
From the tool's definition Send a message to the most recent opencode session on an instance. Streams the response back in real-time. Set abort=true to stop a running task instead of sending a message.
Attacks that exploit this kind of access
Send a message to the most recent opencode session on an instance. Streams the response back in real-time. Set abort=true to stop a running task instead of sending a message. It is categorised as a Execute tool in the Opencode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Opencode MCP server in PolicyLayer and add a rule for 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 Opencode. Nothing to install.
send 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 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. 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 is provided by the Opencode MCP server (klutometis/opencode-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 →