replay_status

Get current replay mode status

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What replay_status does on TradingView MCP Server

AI agents call replay_status to retrieve information from TradingView MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why replay_status is rated Low

This tool queries the current state of TradingView's replay mode without modifying, executing operations, or triggering external effects. It retrieves information only, making it a Read category tool with low severity since querying replay status poses minimal security risk even if misused.

From the tool's definition Tool name 'replay_status' and description 'Get current replay mode status' indicate a data retrieval operation with no side effects. The verb 'Get' and 'status' query pattern are characteristic of Read operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

replay_status Allowed

replay_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replay_status": {}
  }
}

ALLOW ONLY 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_status call is checked against it from then on.

FAQ

Questions about replay_status

What does the replay_status tool do? +

Get current replay mode status. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on replay_status? +

Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for replay_status: 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_status? +

replay_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit replay_status? +

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

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

replay_status 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 →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →