Create a new device fleet
AI agents use iot_fleet_create to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
This tool creates a new fleet of IoT devices, which is a reversible write operation. It establishes a new configuration or resource but does not execute arbitrary code on devices, delete data, or move money. The 'medium' severity reflects that an agent misconfiguring a fleet could cause operational issues, but the action is reversible through updates or deletion.
From the tool's definition Tool name 'iot_fleet_create' and description 'Create a new device fleet' indicate data creation that modifies system state by adding a new fleet entity.
Attacks that exploit this kind of access
Create a new device fleet. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_fleet_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the iot_fleet_create 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_create. 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_create 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.