Toggle autoplay in replay mode, optionally set speed
AI agents invoke replay_autoplay to trigger actions in Tradingview. 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.
This tool triggers an external operation within the TradingView Desktop app via Chrome DevTools Protocol — it controls playback state and speed in replay mode. It doesn't merely read data, nor does it write/delete persistent data; it executes an action that affects the running application's behavior. Misuse could disrupt chart analysis workflows but has limited blast radius.
From the tool's definition Toggle autoplay in replay mode, optionally set speed
Attacks that exploit this kind of access
Toggle autoplay in replay mode, optionally set speed. It is categorised as a Execute tool in the Tradingview 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_autoplay: 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. Nothing to install.
replay_autoplay 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_autoplay 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_autoplay. 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_autoplay is provided by the Tradingview MCP server (lionfaion/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 →