broadcast_agent_update
Broadcast a status update to all active agents. Unlike send_agent_message (point-to-point), this creates a message with no specific recipient that all agents can see via check_agent_inbox. Useful for announcing blockers, completed milestones, or coordination changes.
This record as markdown: /tools/io-github-homenshum-nodebench/broadcast-agent-update.md
What broadcast_agent_update does on Nodebench
AI agents use broadcast_agent_update 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 broadcast_agent_update is rated Medium
This tool writes communication data to a shared system state that affects agent behavior and coordination. While not destructive (messages can be cleared) or executable (doesn't run code), it modifies system state by injecting information into an agent inbox system.
From the tool's definition Tool creates a message artifact that is persisted and visible to multiple agents via check_agent_inbox. The description states it 'broadcast[s] a status update' and 'creates a message', indicating data creation/modification rather than retrieval or deletion.
Attacks that exploit this kind of access
The rule that runs broadcast_agent_update 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 broadcast_agent_update, this is the rule to start with:
broadcast_agent_update 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 broadcast_agent_update call is checked against it from then on.
Questions about broadcast_agent_update
Broadcast a status update to all active agents. Unlike send_agent_message (point-to-point), this creates a message with no specific recipient that all agents can see via check_agent_inbox. Useful for announcing blockers, completed milestones, or coordination changes. 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 broadcast_agent_update: 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.
broadcast_agent_update 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 broadcast_agent_update 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 broadcast_agent_update. 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.
broadcast_agent_update 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