delete_bot

Archive (soft-delete) a bot/strategy. The bot status is set to ARCHIVED and it disappears from the list.

SERVER:GT Protocol MCP Server SOURCEgt-protocol/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gt-protocol-mcp/delete-bot.md

WHAT IT DOES

What delete_bot does on :GT Protocol MCP Server

AI agents call delete_bot to permanently remove resources in :GT Protocol MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_bot is rated Critical

Although described as a 'soft-delete' (status set to ARCHIVED rather than permanent deletion), the bot disappears from active listings and is effectively removed from operational use. This is a destructive action that disables a trading bot/strategy irreversibly in practical terms — restoring it would require explicit intervention.

From the tool's definition Archive (soft-delete) a bot/strategy. The bot status is set to ARCHIVED and it disappears from the list.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_bot Hidden

delete_bot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_bot"
  ]
}

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

FAQ

Questions about delete_bot

What does the delete_bot tool do? +

Archive (soft-delete) a bot/strategy. The bot status is set to ARCHIVED and it disappears from the list. It is categorised as a Destructive tool in the :GT Protocol MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_bot? +

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

delete_bot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_bot? +

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

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

delete_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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →