iot_fleet_remove_device

Remove a device from a fleet

Server Ruflo ruvnet/ruflo
Category Destructive
Risk class Critical
Parameters 00 required

What iot_fleet_remove_device does on Ruflo

AI agents call iot_fleet_remove_device to permanently remove resources in Ruflo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why iot_fleet_remove_device needs a policy

This tool permanently removes a device from fleet management, which cannot be undone without re-provisioning. While not a traditional data deletion, removing an IoT device from a fleet is a destructive operational action that disrupts service and cannot be easily reversed.

From the tool's definition 'Remove a device from a fleet' describes an irreversible deletion action on fleet infrastructure. The verb 'remove' in the context of IoT device management indicates permanent deletion or deprovisioning of a device from operational control.

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 Ruflo 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 Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

iot_fleet_remove_device is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.