Get current UI state: which panels are open, what buttons are visible/enabled/disabled
AI agents call tv_ui_state 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.
This tool only retrieves and reports the current state of UI elements. It performs no side effects, creates no data, executes no code, and cannot delete or move money. It is a straightforward read operation analogous to a status check or query. The low severity reflects minimal blast radius—misuse would only leak information about the current UI state, not cause operational harm.
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' indicate a read-only query operation that retrieves display state information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access tv_ui_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for tv_ui_state:
{
"version": "1",
"default": "deny",
"tools": {
"tv_ui_state": {}
}
}tv_ui_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
tv_ui_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
tv_ui_state is provided by the TradingView MCP Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.