New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ui_fullscreen

Toggle TradingView fullscreen mode

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/ui-fullscreen.md

What ui_fullscreen does on TradingView MCP Server

AI agents invoke ui_fullscreen to trigger actions in TradingView MCP Server. 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.

Why ui_fullscreen is rated High

This tool executes a UI action (toggling fullscreen mode) in an external application via Chrome DevTools Protocol. It's not a read operation, nor does it create/modify persistent data, delete anything, or involve finances. It triggers an external operation (UI automation), placing it in the Execute category. The blast radius is low as it only affects the display state of the TradingView window.

From the tool's definition Toggle TradingView fullscreen mode — triggers a UI state change in TradingView Desktop via Chrome DevTools Protocol

Questions about ui_fullscreen

What does the ui_fullscreen tool do? +

Toggle TradingView fullscreen mode. It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ui_fullscreen? +

Register the TradingView MCP Server 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 Server. Nothing to install.

What risk level is ui_fullscreen? +

ui_fullscreen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ui_fullscreen? +

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.

How do I block ui_fullscreen completely? +

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.

What MCP server provides ui_fullscreen? +

ui_fullscreen is provided by the TradingView MCP Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on TradingView MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TradingView MCP Server's. Pull the full record:

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.