replay_start
Start bar replay mode, optionally at a specific date
This record as markdown: /tools/byeung888-tradingview-mcp/replay-start.md
What replay_start does on TradingView MCP Bridge
AI agents invoke replay_start to trigger actions in TradingView MCP Bridge. 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_start is rated High
This tool executes a command that changes the state and behavior of the TradingView application (entering replay mode). While not destructive or financial, it actively triggers external operations whose effects depend on provided arguments (the optional date parameter).
From the tool's definition Tool 'replay_start' initiates bar replay mode in TradingView, which is an active operation that triggers a specific workflow state in the application.
Attacks that exploit this kind of access
The rule that runs replay_start safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replay_start, this is the rule to start with:
replay_start 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 Bridge, apply this rule, and every replay_start call is checked against it from then on.
Questions about replay_start
Start bar replay mode, optionally at a specific date. It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for replay_start: 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 Bridge. Nothing to install.
replay_start 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_start 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_start. 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_start is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.
Across the catalogue