gt_agents

List Gas Town agents with optional role and rig filters

SERVERRuflo SOURCEruvnet/ruflo

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/ruflo/gt-agents.md

WHAT IT DOES

What gt_agents does on Ruflo

AI agents call gt_agents to retrieve information from Ruflo 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_agents is rated Low

This tool retrieves and filters agent data for querying purposes. It has no side effects, does not execute operations, and does not modify, delete, or create resources. It is a straightforward read operation that returns information about agents matching specified criteria.

From the tool's definition Tool name and description indicate a list operation: 'List Gas Town agents with optional role and rig filters'. The verb 'List' and the filter parameters (role, rig) suggest a query that retrieves information without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gt_agents 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_agents, this is the rule to start with:

gt_agents Allowed

gt_agents 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_agents": {}
  }
}

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

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

FAQ

Questions about gt_agents

What does the gt_agents tool do? +

List Gas Town agents with optional role and rig filters. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gt_agents? +

Register the Ruflo MCP server in PolicyLayer and add a rule for gt_agents: 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.

What risk level is gt_agents? +

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

Can I rate-limit gt_agents? +

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

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

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

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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