ui_fullscreen · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What ui_fullscreen does on TradingView MCP Bridge

AI agents invoke ui_fullscreen to trigger actions in TradingView MCP Bridge. 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 IT NEEDS A POLICY

Why ui_fullscreen needs a policy

This tool triggers an external UI action (toggling fullscreen mode) in a running application. It doesn't read data, write/create data, destroy data, or involve finances. It executes a browser/desktop UI interaction, making Execute the correct category. Severity is low as misuse only affects display state and is easily reversible.

From the tool's definition Toggle TradingView fullscreen mode — triggers an external UI operation on the TradingView Desktop application via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_fullscreen Rate-limited

ui_fullscreen stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_fullscreen": {
      "limits": [
        {
          "counter": "ui_fullscreen_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TradingView MCP Bridge, so you can run agents against it safely.

FAQ

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 Bridge 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 Bridge 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 Bridge. 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 Bridge MCP server (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

ui_fullscreen is one line of TradingView MCP Bridge's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →