iot_fleet_remove_device

Remove a device from 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-remove-device.md

WHAT IT DOES

What iot_fleet_remove_device does on Claude Flow

AI agents call iot_fleet_remove_device 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_remove_device is rated Critical

Removing a device from a fleet is a destructive action because it permanently severs the device's registration and fleet membership, which typically cannot be recovered without manual re-provisioning. While not deleting the physical device, the operation irreversibly modifies state in a way that disrupts service continuity.

From the tool's definition Tool name contains 'remove' and description states 'Remove a device from a fleet' — removal of a device from fleet management is an irreversible operation that cannot be easily undone and results in loss of device registration/association.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iot_fleet_remove_device 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_remove_device, this is the rule to start with:

iot_fleet_remove_device Hidden

iot_fleet_remove_device 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_remove_device"
  ]
}

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_remove_device call is checked against it from then on.

FAQ

Questions about iot_fleet_remove_device

What does the iot_fleet_remove_device tool do? +

Remove a device from 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_remove_device? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_fleet_remove_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.

What risk level is iot_fleet_remove_device? +

iot_fleet_remove_device 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_remove_device? +

Yes. Add a rate_limit block to the iot_fleet_remove_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.

How do I block iot_fleet_remove_device completely? +

Set action: deny in the PolicyLayer policy for iot_fleet_remove_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.

What MCP server provides iot_fleet_remove_device? +

iot_fleet_remove_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.

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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

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