This record as markdown: /tools/ruflo/iot-device-unpair.md
What iot_device_unpair does on Ruflo
AI agents call iot_device_unpair 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_device_unpair is rated Critical
Unpairing a device breaks the established association between the system and the IoT device. This action is destructive in nature because it removes a registered binding that cannot be automatically restored; re-pairing would require deliberate manual intervention. In the context of an autonomous multi-agent swarm, an AI agent misusing this tool could disconnect critical IoT devices at scale, making it high severity.
From the tool's definition 'Unpair from a registered device' — unpairing removes the device registration/association, which is typically irreversible without manual re-pairing
Attacks that exploit this kind of access
The rule that runs iot_device_unpair safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iot_device_unpair, this is the rule to start with:
iot_device_unpair is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every iot_device_unpair call is checked against it from then on.
Questions about iot_device_unpair
Unpair from a registered device. 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.
Register the Ruflo MCP server in PolicyLayer and add a rule for iot_device_unpair: 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.
iot_device_unpair 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_device_unpair 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_device_unpair. 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_device_unpair 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.
More on Ruflo, and thousands of servers like it.
Across the catalogue