replay_step · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What replay_step does on TradingView MCP Bridge

AI agents invoke replay_step 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_step needs a policy

The tool drives an interactive action in TradingView Desktop (advancing the replay by one bar), which is an externally triggered operation affecting application state. It doesn't merely read data, nor does it write/delete persistent data or move money. Execute is the most appropriate category. Severity is low because the blast radius is limited to a chart replay session with no persistent or financial consequences.

From the tool's definition 'Advance one bar in replay mode' — triggers an external operation (stepping the TradingView chart replay forward) that changes the state of the application UI

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replay_step Rate-limited

replay_step 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_step": {
      "limits": [
        {
          "counter": "replay_step_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_step

What does the replay_step tool do? +

Advance one bar in replay mode. 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_step? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for replay_step: 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_step? +

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

Can I rate-limit replay_step? +

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

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

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