gt_convoy_create · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What gt_convoy_create does on Claude Flow

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

WHY IT NEEDS A POLICY

Why gt_convoy_create needs a policy

This tool creates a new work order object ('convoy') in the system, which is a reversible write operation. It does not execute arbitrary code, delete data, or commit financial transactions. The 'medium' severity reflects that misuse could create unwanted tracking records or disrupt workflow coordination, but the blast radius is limited to data creation rather than destruction or external system calls.

From the tool's definition Tool name contains 'create' and description states 'Create a convoy (work order)' — indicates creation of a new data entity for tracking and coordination purposes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gt_convoy_create Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gt_convoy_create": {
      "limits": [
        {
          "counter": "gt_convoy_create_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about gt_convoy_create

What does the gt_convoy_create tool do? +

Create a convoy (work order) for tracking and coordinating multiple beads. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gt_convoy_create? +

Register the Claude Flow 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 Claude Flow. Nothing to install.

What risk level is gt_convoy_create? +

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

Can I rate-limit gt_convoy_create? +

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.

How do I block gt_convoy_create completely? +

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.

What MCP server provides gt_convoy_create? +

gt_convoy_create is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.