send_keys

THE RISK

High Risk

Why send_keys needs a policy

This tool triggers keyboard input on the desktop, including powerful system-level combinations like ctrl+shift+p (command palettes), ctrl+s (save), or even alt+F4 (close window). It executes actions with real effects on running applications.

From the tool's definition Send a key or key-combination (e.g. 'enter', 'ctrl+s', 'ctrl+shift+p')

Documented attack patterns abuse exactly the kind of access send_keys gives an agent:

POLICY

How to control send_keys

PolicyLayer is an MCP gateway — it sits between your AI agents and Openowl, and nothing reaches the server without passing your rules. This is the rule we recommend for send_keys:

policy.json

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

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

Create a free account and register Openowl — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Openowl tools

Destructive delete_workflow_tool Delete a saved workflow. Execute launch_app Launch an application. Execute start_watcher start_watcher Execute stop_watcher Stop the notification watcher. Execute wait_for_change Wait until the screen content changes or timeout elapses. Execute batch_actions batch_actions Execute focus_window Find a window by partial title and focus, minimize, maximize, or restore it. Execute hover Move the mouse cursor to a position without clicking. Useful for revealing tooltips.

All 40 Openowl tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Openowl → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about send_keys

What does the send_keys tool do? +

Send a key or key-combination (e.g. 'enter', 'ctrl+s', 'ctrl+shift+p'). It is categorised as a Execute tool in the Openowl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_keys? +

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

What risk level is send_keys? +

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

Can I rate-limit send_keys? +

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

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

send_keys is provided by the Openowl MCP server (mihir-kanzariya/openowl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openowl tool call.

Start from Openowl, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →