High Risk →

ui_type_text

Type text into the currently focused input/textarea element

How to control ui_type_text ↓

AI agents invoke ui_type_text 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.

High Risk

This tool performs a browser automation action (typing text) via CDP, which constitutes executing an external operation with effects that depend on arguments. It could be used to submit forms, enter commands, or manipulate UI state in TradingView Desktop, making it Execute rather than just Write since it drives live browser interactions.

From the tool's definition 'Type text into the currently focused input/textarea element' — this triggers a browser/UI action via Chrome DevTools Protocol that injects keystrokes into an active element

Documented attack patterns abuse exactly the kind of access ui_type_text gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for ui_type_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_type_text": {
      "limits": [
        {
          "counter": "ui_type_text_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register TradingView MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ui_type_text tool do? +

Type text into the currently focused input/textarea element. 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_type_text? +

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

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

Can I rate-limit ui_type_text? +

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

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

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

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.