gt_convoy_status

Check the status of one or all convoys including progress metrics

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/gt-convoy-status.md

WHAT IT DOES

What gt_convoy_status does on Claude Flow

AI agents call gt_convoy_status to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gt_convoy_status is rated Low

This is a read-only query operation that retrieves status and progress information about convoys. It has no side effects, does not modify data, execute code, delete resources, or commit financial obligations. The blast radius of misuse is minimal—an agent could only inspect convoy states, not alter them.

From the tool's definition Tool name and description indicate a status-checking operation: 'Check the status of one or all convoys including progress metrics' with no mention of modifications, deletions, or external execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gt_convoy_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gt_convoy_status, this is the rule to start with:

gt_convoy_status Allowed

gt_convoy_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gt_convoy_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every gt_convoy_status call is checked against it from then on.

FAQ

Questions about gt_convoy_status

What does the gt_convoy_status tool do? +

Check the status of one or all convoys including progress metrics. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gt_convoy_status? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for gt_convoy_status: 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_status? +

gt_convoy_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gt_convoy_status? +

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

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

gt_convoy_status 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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →