This record as markdown: /tools/ruflo/gt-sling.md
What gt_sling does on Ruflo
AI agents use gt_sling 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 gt_sling is rated Medium
The tool assigns (slings) a bead (work item/task) to an agent for processing. This is a Write operation — it creates an assignment or queues a task in the system. It does not delete data (not Destructive), run arbitrary code directly (not Execute in the strictest sense), or move money (not Financial).
From the tool's definition 'Sling (assign) a bead to a Gas Town agent for processing' — assigns/queues a work item to an agent
Attacks that exploit this kind of access
The rule that runs gt_sling safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gt_sling, this is the rule to start with:
gt_sling 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every gt_sling call is checked against it from then on.
Questions about gt_sling
Sling (assign) a bead to a Gas Town agent for processing. 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.
Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue