Delete a fleet
AI agents call iot_fleet_delete to permanently remove resources in Claude Flow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a destructive action that cannot be undone: deleting an entire fleet of IoT devices or their configuration. Even though it operates on a fleet abstraction rather than individual records, the deletion is irreversible and affects multiple resources. This qualifies as Destructive rather than Write because deletion is not reversible.
From the tool's definition Tool name contains 'delete' and description states 'Delete a fleet' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a fleet. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_fleet_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the iot_fleet_delete 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_delete. 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_delete 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.