computer_type
Type text at the current focus (newlines become Return presses). Requires approval (risk 3).
This record as markdown: /tools/yuga-hashimoto-localant/computer-type.md
What computer_type does on LocalAnt
AI agents invoke computer_type to trigger actions in LocalAnt. 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 computer_type is rated High
This tool simulates keyboard input on the local machine, which constitutes an external operation/browser or desktop automation action. It could be used to inject arbitrary text or commands into focused applications (e.g., a terminal, code editor, browser address bar), making it an Execute-category risk.
From the tool's definition 'Type text at the current focus (newlines become Return presses)' — triggers keyboard input actions on the host PC; 'Requires approval (risk 3)'
Attacks that exploit this kind of access
The rule that runs computer_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For computer_type, this is the rule to start with:
computer_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 LocalAnt, apply this rule, and every computer_type call is checked against it from then on.
Questions about computer_type
Type text at the current focus (newlines become Return presses). Requires approval (risk 3). It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LocalAnt MCP server in PolicyLayer and add a rule for computer_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 LocalAnt. Nothing to install.
computer_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 computer_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 computer_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.
computer_type is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue