Get raw fleet status data
AI agents call fleet_status to retrieve information from OpenClaude MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves fleet monitoring data from the control plane without modifying, deleting, or executing operations. It falls squarely into the Read category as a status query operation. The blast radius of misuse is minimal—an agent could only observe fleet state, not alter it. Severity is low because status data exposure has limited security impact in isolation.
From the tool's definition Tool name 'fleet_status' and description 'Get raw fleet status data' indicate a query/retrieval operation with no side effects. The verb 'Get' and the passive nature of status retrieval (monitoring/observational) are consistent with Read operations.
Attacks that exploit this kind of access
Get raw fleet status data. It is categorised as a Read tool in the OpenClaude MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenClaude MCP Server MCP server in PolicyLayer and add a rule for 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 OpenClaude MCP Server. Nothing to install.
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 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 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.
fleet_status is provided by the OpenClaude MCP Server MCP server (sandraschi/openclaude-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 →