List all fleets
AI agents call iot_fleet_list to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates existing IoT fleet data without creating, modifying, deleting, or executing any external operations. This is a simple informational query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name includes 'list' and description states 'List all fleets' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all fleets. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_fleet_list: 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 Claude Flow. Nothing to install.
iot_fleet_list 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 iot_fleet_list 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 iot_fleet_list. 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.
iot_fleet_list is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.