Execute a trade action in replay mode (buy, sell, or close position)
AI agents invoke replay_trade to trigger actions in TradingView MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Although labeled 'replay mode' (suggesting a simulated environment), the tool executes trade actions (buy, sell, close position) which are Execute-category operations that trigger external trading systems. Even in replay mode, such tools can have significant side effects if misconfigured or if replay mode transitions to live trading.
From the tool's definition Tool description states 'Execute a trade action in replay mode (buy, sell, or close position)' - the verb 'execute' combined with financial actions (buy, sell, close position) indicates this triggers external operations with real consequences in a trading…
Attacks that exploit this kind of access
Execute a trade action in replay mode (buy, sell, or close position). It is categorised as a Execute tool in the TradingView MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP server in PolicyLayer and add a rule for replay_trade: 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 TradingView MCP. Nothing to install.
replay_trade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the replay_trade 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 replay_trade. 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.
replay_trade is provided by the TradingView MCP server (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →