press_hotkey

A execute tool on the Aos MCP server.

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/press-hotkey.md

WHAT IT DOES

What press_hotkey does on Aos

AI agents invoke press_hotkey to trigger actions in Aos. 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.

RISK

Why press_hotkey is rated High

Pressing hotkeys on a desktop can trigger arbitrary system actions (e.g., closing windows, opening terminals, executing commands). This falls under Execute since it triggers external operations on the desktop. The description is empty, reducing confidence, but the server context and tool name strongly imply keyboard-based desktop control.

From the tool's definition Tool name 'press_hotkey' on a server that 'enables AI assistants to control Ubuntu desktops through screenshots, mouse clicks, and keyboard interactions'. Sibling tools include execute_workflow, click_screen, drag_mouse.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs press_hotkey safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For press_hotkey, this is the rule to start with:

press_hotkey Rate-limited

press_hotkey 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "press_hotkey": {
      "limits": [
        {
          "counter": "press_hotkey_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every press_hotkey call is checked against it from then on.

FAQ

Questions about press_hotkey

What does the press_hotkey tool do? +

press_hotkey is a execute tool on the Aos MCP server. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on press_hotkey? +

Register the Aos MCP server in PolicyLayer and add a rule for press_hotkey: 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 Aos. Nothing to install.

What risk level is press_hotkey? +

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

Can I rate-limit press_hotkey? +

Yes. Add a rate_limit block to the press_hotkey 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 press_hotkey completely? +

Set action: deny in the PolicyLayer policy for press_hotkey. 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 press_hotkey? +

press_hotkey is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →