ui_type
Types text into the focused control (or focuses element_ref first, then types). Sends real key events so validation/handlers fire. Requires Accessibility permission.
This record as markdown: /tools/com-local-mcp-local-mcp/ui-type.md
What ui_type does on Local
AI agents invoke ui_type to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | The text to type. |
element_ref | string | — | Optional; focus this element first. |
Parameters from the server's own tool schema.
Why ui_type is rated High
This tool sends real key events to UI controls, triggering actual validation and event handlers. This constitutes executing real UI interactions that can have side effects beyond simple data entry — including triggering form submissions, activating workflows, or modifying application state.
From the tool's definition 'Types text into the focused control', 'Sends real key events so validation/handlers fire'
Attacks that exploit this kind of access
The rule that runs ui_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_type, this is the rule to start with:
ui_type 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 Local, apply this rule, and every ui_type call is checked against it from then on.
Questions about ui_type
Types text into the focused control (or focuses element_ref first, then types). Sends real key events so validation/handlers fire. Requires Accessibility permission. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ui_type accepts 2 parameters: text, element_ref. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for ui_type: 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 Local. Nothing to install.
ui_type 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_type 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_type. 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_type is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue