This record as markdown: /tools/ruflo/iot-fleet-create.md
What iot_fleet_create does on Ruflo
AI agents use iot_fleet_create 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 iot_fleet_create is rated Medium
This tool creates new resources (device fleets) which is a reversible data modification operation. It falls into the Write category rather than Execute because it creates abstract resource configurations rather than triggering arbitrary external code execution.
From the tool's definition Tool name 'iot_fleet_create' and description 'Create a new device fleet' indicate a create/write operation that establishes new IoT device infrastructure.
Attacks that exploit this kind of access
The rule that runs iot_fleet_create 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_fleet_create, this is the rule to start with:
iot_fleet_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every iot_fleet_create call is checked against it from then on.
Questions about iot_fleet_create
Create a new device 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.
Register the Ruflo MCP server in PolicyLayer and add a rule for iot_fleet_create: 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_fleet_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the iot_fleet_create 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_fleet_create. 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_fleet_create 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.
This server
Across the catalogue