Types the given text on the Ubuntu VM.
AI agents invoke type_text to trigger actions in Ubuntu VM Control. 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.
Typing text on a remote VM is an active interaction that can have significant side effects depending on the active context (e.g., typing into a terminal executes commands, typing into a browser navigates to URLs, typing into a file editor modifies content). It is an external operation whose effects depend on arguments and the current state of the VM, placing it in the Execute category.
From the tool's definition 'Types the given text on the Ubuntu VM' — simulates keyboard input on a remote VM, which can trigger commands, interact with GUI applications, or inject text into active windows.
Attacks that exploit this kind of access
Types the given text on the Ubuntu VM. It is categorised as a Execute tool in the Ubuntu VM Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ubuntu VM Control MCP server in PolicyLayer and add a rule for 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 Ubuntu VM Control. Nothing to install.
type_text 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 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.
Set action: deny in the PolicyLayer policy for 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.
type_text is provided by the Ubuntu VM Control MCP server (ltcg-addict/ubuntu). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →