Press keys/chords: ['Enter'], ['ctrl','a'], ['ctrl+l','Return'].
AI agents invoke keypress to trigger actions in Linux Computer Use. 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.
Sending arbitrary keypresses or keyboard chords to a desktop environment can trigger any application action — launching programs, executing commands, deleting files, submitting forms, or interacting with system dialogs. This constitutes executing operations whose effects are entirely argument-dependent and can have wide blast radius on a live desktop.
From the tool's definition Press keys/chords: ['Enter'], ['ctrl','a'], ['ctrl+l','Return']
Attacks that exploit this kind of access
Press keys/chords: ['Enter'], ['ctrl','a'], ['ctrl+l','Return']. It is categorised as a Execute tool in the Linux Computer Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Linux Computer Use MCP server in PolicyLayer and add a rule for keypress: 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 Linux Computer Use. Nothing to install.
keypress 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 keypress 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 keypress. 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.
keypress is provided by the Linux Computer Use MCP server (tak-uukti/linux-computer-use). 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 →