os_hotkey · OScribe MCP: Risk & Policy

WHAT IT DOES

What os_hotkey does on OScribe

AI agents invoke os_hotkey to trigger actions in OScribe. 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 os_hotkey needs a policy

Pressing hotkeys triggers application actions on the user's desktop. Hotkeys can execute arbitrary operations (e.g., Ctrl+S to save, Alt+F4 to close, Ctrl+Z to undo, or even system-level shortcuts). In the context of a desktop automation server, misuse could trigger destructive or unintended actions across any application, making this an Execute category tool with high severity.

From the tool's definition 'Press a keyboard shortcut' — executes keyboard combinations on the desktop

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

os_hotkey Rate-limited

os_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": {
    "os_hotkey": {
      "limits": [
        {
          "counter": "os_hotkey_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 OScribe, so you can run agents against it safely.

FAQ

Questions about os_hotkey

What does the os_hotkey tool do? +

Press a keyboard shortcut. It is categorised as a Execute tool in the OScribe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on os_hotkey? +

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

What risk level is os_hotkey? +

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

Can I rate-limit os_hotkey? +

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

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

os_hotkey is provided by the OScribe MCP server (mikealkeal/oscribe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.