gt_convoy_track · Ruflo MCP: Risk & Policy

WHAT IT DOES

What gt_convoy_track does on Ruflo

AI agents use gt_convoy_track 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 gt_convoy_track needs a policy

The tool creates or modifies data (adding/removing issues from a convoy) in a reversible way. Removing an issue from a convoy is not necessarily irreversible (it could be re-added), so Write is the most appropriate category. Severity is medium because misuse could disrupt convoy/workflow coordination across agents in a multi-agent swarm.

From the tool's definition "Add or remove issues from an existing convoy" — modifies the membership/contents of an existing convoy object

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gt_convoy_track Rate-limited

gt_convoy_track 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_track": {
      "limits": [
        {
          "counter": "gt_convoy_track_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 gt_convoy_track

What does the gt_convoy_track tool do? +

Add or remove issues from an existing convoy. 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 gt_convoy_track? +

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

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

Can I rate-limit gt_convoy_track? +

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

Set action: deny in the PolicyLayer policy for gt_convoy_track. 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_track? +

gt_convoy_track 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

gt_convoy_track 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 →