list_bots

List all user

SERVER:GT Protocol MCP Server SOURCEgt-protocol/mcp

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/gt-protocol-mcp/list-bots.md

WHAT IT DOES

What list_bots does on :GT Protocol MCP Server

AI agents call list_bots to retrieve information from :GT Protocol MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_bots is rated Low

This tool retrieves and displays existing bot configurations but does not create, modify, delete, or execute trades. While the server context involves financial trading, this specific tool is a passive query operation with no side effects. The incomplete description ('List all user') limits confidence slightly, but the name and context clearly indicate a read operation.

From the tool's definition Tool name is 'list_bots' and description indicates it lists user bots without modification. The verb 'list' is a read-only retrieval operation.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_bots safely

PolicyLayer is an MCP gateway: it sits between your AI agents and :GT Protocol MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_bots, this is the rule to start with:

list_bots Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect :GT Protocol MCP Server, apply this rule, and every list_bots call is checked against it from then on.

FAQ

Questions about list_bots

What does the list_bots tool do? +

List all user. It is categorised as a Read tool in the :GT Protocol MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_bots? +

Register the :GT Protocol MCP Server MCP server in PolicyLayer and add a rule for list_bots: 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 :GT Protocol MCP Server. Nothing to install.

What risk level is list_bots? +

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

Can I rate-limit list_bots? +

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

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

list_bots is provided by the :GT Protocol MCP Server MCP server (gt-protocol/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on :GT Protocol MCP Server, and thousands of servers like it.

This server

All 19 :GT Protocol MCP Server tools →

Across the catalogue

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

Guides

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