replay_stop · TradingView MCP: Risk & Policy

WHAT IT DOES

What replay_stop does on TradingView MCP

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

WHY IT NEEDS A POLICY

Why replay_stop needs a policy

This tool executes a state-changing command in TradingView Desktop via Chrome DevTools Protocol. While stopping a replay session is not destructive (the replay data is not deleted) and not financial (no money moves), it performs an irreversible action that affects the live trading environment by transitioning from replay mode back to realtime.

From the tool's definition Tool name 'replay_stop' and description 'Stop replay and return to realtime' indicate it triggers an external operation (halting replay mode and switching TradingView state) whose effects depend on the current replay session context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replay_stop Rate-limited

replay_stop 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_stop": {
      "limits": [
        {
          "counter": "replay_stop_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 MCP, so you can run agents against it safely.

FAQ

Questions about replay_stop

What does the replay_stop tool do? +

Stop replay and return to realtime. 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.

How do I enforce a policy on replay_stop? +

Register the TradingView MCP server in PolicyLayer and add a rule for replay_stop: 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.

What risk level is replay_stop? +

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

Can I rate-limit replay_stop? +

Yes. Add a rate_limit block to the replay_stop 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_stop completely? +

Set action: deny in the PolicyLayer policy for replay_stop. 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_stop? +

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