replay_stop · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What replay_stop does on TradingView MCP Bridge

AI agents invoke replay_stop 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 IT NEEDS A POLICY

Why replay_stop needs a policy

This tool triggers an action that changes the operational state of TradingView's charting system. While not destructive (the replay can be restarted) or financial in nature, it executes a command with external effects on the trading platform's state.

From the tool's definition Stops an active replay session in TradingView, changing the state of the charting system from replay mode back to realtime. The tool performs an external operation via Chrome DevTools Protocol that alters the runtime state of the application.

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 Bridge, 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 Bridge 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 Bridge 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 Bridge. 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 Bridge MCP server (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.