replay_autoplay
Toggle autoplay in replay mode, optionally set speed
This record as markdown: /tools/debarpan2000-tradingview-mcp/replay-autoplay.md
What replay_autoplay does on TradingView MCP Server
AI agents invoke replay_autoplay to trigger actions in TradingView MCP Server. 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.
Why replay_autoplay is rated High
This tool triggers an external operation within TradingView Desktop (controlling replay playback state and speed), which is an action that executes a UI/application behavior. It doesn't merely read data, nor does it create/modify persistent data reversibly. It falls under Execute as it drives application behavior via Chrome DevTools Protocol.
From the tool's definition Toggle autoplay in replay mode, optionally set speed
Attacks that exploit this kind of access
The rule that runs replay_autoplay safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replay_autoplay, this is the rule to start with:
replay_autoplay stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every replay_autoplay call is checked against it from then on.
Questions about replay_autoplay
Toggle autoplay in replay mode, optionally set speed. It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Server 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 MCP Server. 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 MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Server, and thousands of servers like it.
Across the catalogue