ui_type

Type text into the currently focused field using simulated keystrokes via System Events. Optionally activate a specific app first. Requires Accessibility permissions.

SERVERAirMCP SOURCEairmcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/ui-type.md

What ui_type does on AirMCP

AI agents invoke ui_type to trigger actions in AirMCP. 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_type is rated High

This tool simulates keyboard input into whatever field currently has focus, which is an external operation whose effects entirely depend on context and arguments. It can type into any application — including terminal, password fields, forms, or chat — making it high severity since an AI agent could inject arbitrary text into sensitive or dangerous contexts.

From the tool's definition 'Type text into the currently focused field using simulated keystrokes via System Events' — this triggers external OS-level input simulation via accessibility APIs

Questions about ui_type

What does the ui_type tool do? +

Type text into the currently focused field using simulated keystrokes via System Events. Optionally activate a specific app first. Requires Accessibility permissions. It is categorised as a Execute tool in the AirMCP 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? +

Register the Air 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 AirMCP. Nothing to install.

What risk level is ui_type? +

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

Can I rate-limit ui_type? +

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.

How do I block ui_type completely? +

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.

What MCP server provides ui_type? +

ui_type is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Air, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Air's. Pull the full record:

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.