replay_status

Get current replay mode status

Server TradingView MCP Bridge thinhbv/tradingview_mcp
Category Read
Risk class Low
Parameters 00 required

What replay_status does on TradingView MCP Bridge

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

Why replay_status needs a policy

This tool retrieves the current status of replay mode, which is a read-only operation with no side effects. It does not modify chart state, execute trades, create/delete alerts, or run scripts. The action is purely informational, consistent with the Read category for retrieval/query operations.

From the tool's definition Tool name 'replay_status' and description 'Get current replay mode status' indicate a query operation that retrieves state information without modifying data or triggering external actions.

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 Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on replay_status? +

Register the TradingView MCP Bridge 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 Bridge. 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 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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.