# update_bot

Update settings of an existing bot/strategy.

Agent View of the PolicyLayer registry record for `update_bot`. HTML page: https://policylayer.com/tools/gt-protocol-mcp/update-bot

## Facts

- Tool: `update_bot`
- Server: :GT Protocol MCP Server (`gt-protocol/mcp`) — https://policylayer.com/tools/gt-protocol-mcp.md
- Homepage: https://github.com/gt-protocol/mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_bot",
    "arguments": {}
  }
}
```

## Why update_bot is rated Medium

update_bot modifies bot configuration rather than deleting it (reversible = Write, not Destructive). However, given the context of live trading accounts on financial exchanges, unauthorized bot setting changes could cause significant financial losses through altered trading behavior. Severity is high due to the blast radius: misconfigured bots on leveraged trading platforms can rapidly deplete account balances.

From the tool's own definition: "Tool description states 'Update settings of an existing bot/strategy' which is a reversible modification operation."

## Use case

AI agents use update_bot to create or update resources in :GT Protocol MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your :GT Protocol MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches :GT Protocol MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_bot": {
      "limits": [
        {
          "counter": "update_bot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on :GT Protocol MCP Server (18)

- `delete_bot` — Destructive — https://policylayer.com/tools/gt-protocol-mcp/delete-bot.md
- `run_backtest` — Execute — https://policylayer.com/tools/gt-protocol-mcp/run-backtest.md
- `start_bot` — Execute — https://policylayer.com/tools/gt-protocol-mcp/start-bot.md
- `stop_bot` — Execute — https://policylayer.com/tools/gt-protocol-mcp/stop-bot.md
- `close_deal` — Financial — https://policylayer.com/tools/gt-protocol-mcp/close-deal.md
- `start_deal` — Financial — https://policylayer.com/tools/gt-protocol-mcp/start-deal.md
- `authenticate` — Read — https://policylayer.com/tools/gt-protocol-mcp/authenticate.md
- `get_active_deals` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-active-deals.md
- `get_balance` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-balance.md
- `get_bot` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-bot.md
- `get_deal_history` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-deal-history.md
- `get_exchanges` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-exchanges.md
- `get_profile` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-profile.md
- `list_bots` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-bots.md
- `list_deals` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-deals.md
- `list_portfolios` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-portfolios.md
- `create_bot` — Write — https://policylayer.com/tools/gt-protocol-mcp/create-bot.md
- `paper_clone` — Write — https://policylayer.com/tools/gt-protocol-mcp/paper-clone.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=gt-protocol-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/gt-protocol-mcp