Fleet status — returns Prefab UI when available, plain dict otherwise.
AI agents call fleet_dashboard 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 and displays fleet status information without any capability to modify, delete, or execute operations. It is purely informational, returning existing data in UI or dictionary format. There is no indication of side effects, data mutations, or external operations being triggered. This places it squarely in the Read category with low severity.
From the tool's definition Tool name 'fleet_dashboard' and description 'Fleet status — returns Prefab UI when available, plain dict otherwise' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Fleet status — returns Prefab UI when available, plain dict otherwise. 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_dashboard: 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_dashboard 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_dashboard 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_dashboard. 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_dashboard 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 →