# paper_clone

Create a paper trading (demo) copy of an existing live bot.

Agent View of the PolicyLayer registry record for `paper_clone`. HTML page: https://policylayer.com/tools/gt-protocol-mcp/paper-clone

## Facts

- Tool: `paper_clone`
- 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": "paper_clone",
    "arguments": {}
  }
}
```

## Why paper_clone is rated Medium

This is a Write operation because it creates or instantiates new data (a demo bot configuration) reversibly. While the tool operates in a trading context, it specifically uses paper/demo trading which eliminates direct financial risk on real accounts. However, it could be misused to instantiate many bots or consume resources if abused.

From the tool's own definition: "Tool creates a new paper trading bot based on an existing live bot configuration. The description explicitly states 'Create a paper trading (demo) copy', indicating bot creation/instantiation that modifies the user's trading infrastructure."

## Use case

AI agents use paper_clone 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": {
    "paper_clone": {
      "limits": [
        {
          "counter": "paper_clone_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
- `update_bot` — Write — https://policylayer.com/tools/gt-protocol-mcp/update-bot.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