ui_keyboard
Press keyboard keys or shortcuts (e.g., Enter, Escape, Alt+S, Ctrl+Z)
This record as markdown: /tools/byeung888-tradingview-mcp/ui-keyboard.md
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 ui_keyboard is rated High
This tool sends arbitrary keyboard input to the TradingView Desktop application. 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
The rule that runs ui_keyboard safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_keyboard, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every ui_keyboard call is checked against it from then on.
Questions about ui_keyboard
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.
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.
ui_keyboard 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_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.
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.
ui_keyboard is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.
Across the catalogue