iot_fleet_delete

Delete a fleet

SERVERClaude Flow SOURCEclaude-flow

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/iot-fleet-delete.md

WHAT IT DOES

What iot_fleet_delete does on Claude Flow

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.

RISK

Why iot_fleet_delete is rated Critical

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

RECOMMENDED RULE

The rule that runs iot_fleet_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iot_fleet_delete, this is the rule to start with:

iot_fleet_delete Hidden

iot_fleet_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "iot_fleet_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every iot_fleet_delete call is checked against it from then on.

FAQ

Questions about iot_fleet_delete

What does the iot_fleet_delete tool do? +

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.

How do I enforce a policy on iot_fleet_delete? +

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.

What risk level is iot_fleet_delete? +

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.

Can I rate-limit iot_fleet_delete? +

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.

How do I block iot_fleet_delete completely? +

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.

What MCP server provides iot_fleet_delete? +

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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →