get_bot

Get details of a specific strategy/bot by ID.

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/get-bot.md

WHAT IT DOES

What get_bot does on :GT Protocol MCP Server

AI agents call get_bot 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 get_bot is rated Low

This tool queries and returns information about an existing bot/strategy without creating, modifying, deleting, or executing any trades. It is a pure read operation that poses minimal risk if misused by an AI agent—an attacker could learn about bot configurations but cannot alter trading positions, execute deals, or access financial accounts beyond viewing.

From the tool's definition Tool name 'get_bot' and description 'Get details of a specific strategy/bot by ID' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_bot Allowed

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

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 get_bot call is checked against it from then on.

FAQ

Questions about get_bot

What does the get_bot tool do? +

Get details of a specific strategy/bot by ID. 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 get_bot? +

Register the :GT Protocol MCP Server MCP server in PolicyLayer and add a rule for get_bot: 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 get_bot? +

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

Can I rate-limit get_bot? +

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

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

get_bot 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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