gt_beads_create · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What gt_beads_create does on Claude Flow

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

Creating issues/tasks is a reversible write operation—data can be modified or deleted later. The tool modifies system state by adding entries but does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because widespread creation of spurious tasks could degrade system usability and consume resources, but the effect is limited to one application domain and reversible.

From the tool's definition Tool name 'gt_beads_create' and description 'Create a bead (issue/task)' explicitly perform a create operation that adds new data to the Gas Town Beads system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gt_beads_create Rate-limited

gt_beads_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_beads_create": {
      "limits": [
        {
          "counter": "gt_beads_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_beads_create

What does the gt_beads_create tool do? +

Create a bead (issue/task) in the Gas Town Beads system with priority and labels. 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_beads_create? +

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

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

Can I rate-limit gt_beads_create? +

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

Set action: deny in the PolicyLayer policy for gt_beads_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_beads_create? +

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