tv_ui_state

Get current UI state: which panels are open, what buttons are visible/enabled/disabled

SERVERTradingView MCP Bridge SOURCEbyeung888/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/byeung888-tradingview-mcp/tv-ui-state.md

WHAT IT DOES

What tv_ui_state does on TradingView MCP Bridge

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

RISK

Why tv_ui_state is rated Low

This tool only retrieves and queries the current state of the TradingView UI without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it a Read category tool with low severity since it poses minimal risk if misused by an AI agent.

From the tool's definition Tool name 'tv_ui_state' and description 'Get current UI state: which panels are open, what buttons are visible/enabled/disabled' — uses 'Get' verb and describes read-only retrieval of UI visibility and state information with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tv_ui_state safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tv_ui_state, this is the rule to start with:

tv_ui_state Allowed

tv_ui_state 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": {
    "tv_ui_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about tv_ui_state

What does the tv_ui_state tool do? +

Get current UI state: which panels are open, what buttons are visible/enabled/disabled. 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 tv_ui_state? +

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

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

Can I rate-limit tv_ui_state? +

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

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

tv_ui_state is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.

This server

All 78 TradingView MCP Bridge tools →

Across the catalogue

The MCP Attack Database →

Guides

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