replay_stop

Stop replay and return to realtime

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/replay-stop.md

WHAT IT DOES

What replay_stop does on TradingView MCP Server

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

RISK

Why replay_stop is rated High

The tool performs an active operation that modifies the state of an external application (TradingView Desktop). While not destructive (the change is reversible by entering replay mode again) and not a simple data retrieval, it executes a command whose effect depends on the current application state. This fits the Execute category: triggering external operations whose effects depend on context/arguments.

From the tool's definition Tool name 'replay_stop' and description 'Stop replay and return to realtime' indicate an action that triggers a state change in TradingView Desktop via Chrome DevTools Protocol.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs replay_stop 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_stop, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every replay_stop call is checked against it from then on.

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 Server 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 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 Server. 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 MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Server, and thousands of servers like it.

This server

All 78 TradingView MCP Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →