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 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries the current state of the TradingView UI without creating, modifying, deleting, or executing any actions. It returns observational data about the application's visual state. The blast radius if misused by an AI agent is minimal—incorrect interpretation of UI state cannot cause harm beyond potentially taking wrong actions in subsequent tool calls, which would fail gracefully.
From the tool's definition Tool retrieves UI state information (which panels are open, what buttons are visible/enabled/disabled) with no modification or side effects.
Attacks that exploit this kind of access
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 MCP Server, which means it retrieves data without modifying state.
Register the TradingView 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. 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 server (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →