replay_start · Tradingview MCP: Risk & Policy

WHAT IT DOES

What replay_start does on Tradingview

AI agents invoke replay_start 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.

WHY IT NEEDS A POLICY

Why replay_start needs a policy

This tool triggers an external operation (replay mode activation) whose effects depend on the date argument and downstream automation connected to chart state changes. It is not merely reading data (Read) or making reversible modifications to stored settings (Write). Instead, it initiates a procedural simulation that affects how the charting application behaves and may trigger automated actions.

From the tool's definition Start bar replay mode, optionally at a specific date — activates a mode that simulates historical price action replay in TradingView, triggering automated chart state changes and potentially executing dependent workflows (alerts, indicators, scripts).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replay_start Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replay_start": {
      "limits": [
        {
          "counter": "replay_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tradingview, so you can run agents against it safely.

FAQ

Questions about replay_start

What does the replay_start tool do? +

Start bar replay mode, optionally at a specific date. 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.

How do I enforce a policy on replay_start? +

Register the Tradingview 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. Nothing to install.

What risk level is replay_start? +

replay_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit replay_start? +

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.

How do I block replay_start completely? +

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.

What MCP server provides replay_start? +

replay_start 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.