computer_hold_key · Computer Use MCP Server MCP

WHAT IT DOES

What computer_hold_key does on Computer Use MCP Server

AI agents invoke computer_hold_key to trigger actions in Computer Use MCP Server. 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 IT NEEDS A POLICY

Why computer_hold_key needs a policy

This tool simulates keyboard input by holding a key, which can trigger arbitrary system actions depending on which key is held (e.g., holding modifier keys, function keys, or shortcuts). Combined with the broader server context of automating Linux desktop interactions, this constitutes executing external operations whose effects depend on arguments.

From the tool's definition Hold down a key for a specified duration in seconds

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

computer_hold_key Rate-limited

computer_hold_key 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": {
    "computer_hold_key": {
      "limits": [
        {
          "counter": "computer_hold_key_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Computer Use MCP Server, so you can run agents against it safely.

FAQ

Questions about computer_hold_key

What does the computer_hold_key tool do? +

Hold down a key for a specified duration in seconds. It is categorised as a Execute tool in the Computer Use MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on computer_hold_key? +

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

What risk level is computer_hold_key? +

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

Can I rate-limit computer_hold_key? +

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

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

computer_hold_key is provided by the Computer Use MCP Server MCP server (sebastianbaltes/claude_code_computer_use_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

computer_hold_key is one line of Computer Use MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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