Add or remove dependencies between beads
AI agents use gt_beads_dep 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.
The tool creates or removes dependency links between 'beads' (likely workflow or pipeline nodes in the Claude Flow orchestration system). Adding is a Write operation; removing could be considered Destructive, but dependency links are typically reconfigurable/reversible relationships rather than irreversible data deletion.
From the tool's definition 'Add or remove dependencies between beads' — modifies dependency relationships between components
Attacks that exploit this kind of access
Add or remove dependencies between 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.
Register the Claude Flow MCP server in PolicyLayer and add a rule for gt_beads_dep: 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.
gt_beads_dep 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_beads_dep 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_beads_dep. 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_beads_dep 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.