Add a registered device to a fleet
AI agents use iot_fleet_add_device 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 or modifies fleet membership by adding a device, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial).
From the tool's definition Tool name 'iot_fleet_add_device' and description 'Add a registered device to a fleet' indicate a create/modify operation that assigns or registers a device to a fleet group.
Attacks that exploit this kind of access
Add a registered device to a 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_add_device: 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_add_device 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_add_device 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_add_device. 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_add_device 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.