overstory_fleet_status

Read the Overstory multi-agent fleet status — active agents, capabilities, health, worktree state.

SERVERNodebench SOURCEnodebench-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about overstory_fleet_status

What does the overstory_fleet_status tool do? +

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.

How do I enforce a policy on overstory_fleet_status? +

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.

What risk level is overstory_fleet_status? +

overstory_fleet_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit overstory_fleet_status? +

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.

How do I block overstory_fleet_status completely? +

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.

What MCP server provides overstory_fleet_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.