ui_keyboard · TradingView MCP Bridge MCP: Risk & Policy

WHAT IT DOES

What ui_keyboard does on TradingView MCP Bridge

AI agents invoke ui_keyboard 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_keyboard needs a policy

This tool simulates keyboard input on the TradingView desktop application via Chrome DevTools Protocol. Keyboard shortcuts can trigger a wide range of actions depending on context — including saving, deleting, submitting orders, or other irreversible operations.

From the tool's definition Press keyboard keys or shortcuts (e.g., Enter, Escape, Alt+S, Ctrl+Z)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_keyboard Rate-limited

ui_keyboard 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_keyboard": {
      "limits": [
        {
          "counter": "ui_keyboard_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_keyboard

What does the ui_keyboard tool do? +

Press keyboard keys or shortcuts (e.g., Enter, Escape, Alt+S, Ctrl+Z). 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_keyboard? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for ui_keyboard: 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_keyboard? +

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

Can I rate-limit ui_keyboard? +

Yes. Add a rate_limit block to the ui_keyboard 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_keyboard completely? +

Set action: deny in the PolicyLayer policy for ui_keyboard. 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_keyboard? +

ui_keyboard 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.