Toggle TradingView fullscreen mode
AI agents invoke ui_fullscreen to trigger actions in TradingView MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a UI action (toggling fullscreen mode) in an external application. It doesn't read data, write/modify data persistently, or have destructive/financial implications. It's an external operation whose effect is toggling application window state, making Execute the most appropriate category. Severity is low as the blast radius of misuse is minimal — it only changes the display mode of the application.
From the tool's definition Toggle TradingView fullscreen mode — triggers a UI state change in the TradingView Desktop application via Chrome DevTools Protocol
Attacks that exploit this kind of access
Toggle TradingView fullscreen mode. It is categorised as a Execute tool in the TradingView MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP server in PolicyLayer and add a rule for ui_fullscreen: 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.
ui_fullscreen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ui_fullscreen 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 ui_fullscreen. 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.
ui_fullscreen 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 →