iot_device_remove

Remove a registered device

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

WHAT IT DOES

What iot_device_remove does on Claude Flow

AI agents call iot_device_remove 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_device_remove is rated Critical

Removing a registered IoT device is a destructive action that irreversibly deletes or deregisters data. This is more severe than Write (which is reversible) because re-registration would require external intervention and the original device context/configuration may be lost.

From the tool's definition Tool name 'iot_device_remove' and description 'Remove a registered device' indicate irreversible deletion of device registration data. The term 'remove' in IoT context means permanent deregistration, which cannot be undone without manual re-registration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

iot_device_remove Hidden

iot_device_remove 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_device_remove"
  ]
}

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

FAQ

Questions about iot_device_remove

What does the iot_device_remove tool do? +

Remove a registered device. 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_device_remove? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_device_remove: 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_device_remove? +

iot_device_remove 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_device_remove? +

Yes. Add a rate_limit block to the iot_device_remove 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_device_remove completely? +

Set action: deny in the PolicyLayer policy for iot_device_remove. 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_device_remove? +

iot_device_remove 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 →