paper_clone
Create a paper trading (demo) copy of an existing live bot.
This record as markdown: /tools/gt-protocol-mcp/paper-clone.md
What paper_clone does on :GT Protocol MCP Server
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.
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 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.
Attacks that exploit this kind of access
The rule that runs paper_clone 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 paper_clone, this is the rule to start with:
paper_clone stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect :GT Protocol MCP Server, apply this rule, and every paper_clone call is checked against it from then on.
Questions about paper_clone
Create a paper trading (demo) copy of an existing live bot. It is categorised as a Write tool in the :GT Protocol MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the :GT Protocol MCP Server MCP server in PolicyLayer and add a rule for paper_clone: 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.
paper_clone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the paper_clone 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.
Set action: deny in the PolicyLayer policy for paper_clone. 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.
paper_clone 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.
More on :GT Protocol MCP Server, and thousands of servers like it.
This server
Across the catalogue