iot_fleet_add_device · Ruflo MCP: Risk & Policy

WHAT IT DOES

What iot_fleet_add_device does on Ruflo

AI agents use iot_fleet_add_device to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.

WHY IT NEEDS A POLICY

Why iot_fleet_add_device needs a policy

The tool creates or modifies fleet configuration by adding a device association, which is reversible (device can be removed). This is a Write operation rather than Execute because it modifies state declaratively rather than triggering autonomous actions.

From the tool's definition Tool name 'iot_fleet_add_device' and description 'Add a registered device to a fleet' indicate creation/modification of fleet membership state. This is a reversible write operation that modifies IoT fleet configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

iot_fleet_add_device Rate-limited

iot_fleet_add_device stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "iot_fleet_add_device": {
      "limits": [
        {
          "counter": "iot_fleet_add_device_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ruflo, so you can run agents against it safely.

FAQ

Questions about iot_fleet_add_device

What does the iot_fleet_add_device tool do? +

Add a registered device to a fleet. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on iot_fleet_add_device? +

Register the Ruflo MCP server in PolicyLayer and add a rule for iot_fleet_add_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_add_device? +

iot_fleet_add_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit iot_fleet_add_device? +

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

Set action: deny in the PolicyLayer policy for iot_fleet_add_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_add_device? +

iot_fleet_add_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_add_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 →