send_peer_message
Send a direct structured message to a peer without routing everything through a central orchestrator.
This record as markdown: /tools/io-github-homenshum-nodebench/send-peer-message.md
What send_peer_message does on Nodebench
AI agents use send_peer_message to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why send_peer_message is rated Medium
This tool creates and delivers a message, which is a reversible write action. It modifies state (adds a message to a peer's inbox or communication channel) but does not execute code, delete data, or move money.
From the tool's definition Tool description states 'Send a direct structured message to a peer' — a write operation that creates/transmits message data to another entity.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs send_peer_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_peer_message, this is the rule to start with:
send_peer_message 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 Nodebench, apply this rule, and every send_peer_message call is checked against it from then on.
Questions about send_peer_message
Send a direct structured message to a peer without routing everything through a central orchestrator. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for send_peer_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 Nodebench. Nothing to install.
send_peer_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_peer_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_peer_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_peer_message is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue