overstory_fleet_status
Read the Overstory multi-agent fleet status — active agents, capabilities, health, worktree state.
This record as markdown: /tools/io-github-homenshum-nodebench/overstory-fleet-status.md
What overstory_fleet_status does on Nodebench
AI agents call overstory_fleet_status to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why overstory_fleet_status is rated Low
This tool performs read-only status queries of a multi-agent fleet. It retrieves state information (active agents, capabilities, health, worktree state) without creating, modifying, executing, or deleting any data. The 'Read' verb and passive information retrieval nature confirm this is a Read category tool with low severity, as misuse would only expose fleet status information without enabling harmful actions.
From the tool's definition Tool description explicitly states 'Read the Overstory multi-agent fleet status' with operations limited to querying 'active agents, capabilities, health, worktree state' — all informational retrieval with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs overstory_fleet_status 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 overstory_fleet_status, this is the rule to start with:
overstory_fleet_status is read-only, so it stays allowed. 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 overstory_fleet_status call is checked against it from then on.
Questions about overstory_fleet_status
Read the Overstory multi-agent fleet status — active agents, capabilities, health, worktree state. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for overstory_fleet_status: 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.
overstory_fleet_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the overstory_fleet_status 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 overstory_fleet_status. 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.
overstory_fleet_status 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