Sling (assign) a bead to a Gas Town agent for processing
AI agents use gt_sling 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 assigns/routes a work item ('bead') to an agent for processing, which is a write/scheduling operation creating an assignment record. No indication of irreversible deletion, code execution, or financial action. Severity is medium because misrouting work items in an enterprise orchestration system could cause unintended agent actions, but the operation itself appears reversible.
From the tool's definition 'Sling (assign) a bead to a Gas Town agent for processing'
Attacks that exploit this kind of access
Sling (assign) a bead to a Gas Town agent for processing. 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_sling: 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_sling 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_sling 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_sling. 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_sling 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.