gt_convoy_create
Create a convoy (work order) for tracking and coordinating multiple beads
This record as markdown: /tools/ruflo/gt-convoy-create.md
What gt_convoy_create does on Ruflo
AI agents use gt_convoy_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 gt_convoy_create is rated Medium
This tool creates and persists a new work order/convoy object within the Ruflo agent orchestration system. It modifies system state by adding new coordination records but does not execute arbitrary operations, delete data, or move money. The severity is medium because misuse could create many spurious work orders consuming resources, but the operation is reversible (work orders can be terminated or removed).
From the tool's definition Tool name 'gt_convoy_create' and description 'Create a convoy (work order) for tracking and coordinating multiple beads' indicate this creates a new data structure (work order/convoy) in the system.
Attacks that exploit this kind of access
The rule that runs gt_convoy_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 gt_convoy_create, this is the rule to start with:
gt_convoy_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 gt_convoy_create call is checked against it from then on.
Questions about gt_convoy_create
Create a convoy (work order) for tracking and coordinating multiple beads. 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 gt_convoy_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.
gt_convoy_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 gt_convoy_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 gt_convoy_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.
gt_convoy_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