send_keys

Send keystrokes to an element

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/send-keys.md

WHAT IT DOES

What send_keys does on Ncp

AI agents invoke send_keys to trigger actions in Ncp. 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 send_keys is rated High

Sending keystrokes to UI elements constitutes execution of browser/application actions. Depending on the target element, this could trigger form submissions, command execution, navigation, or other operations whose effects depend entirely on context and arguments. Misuse by an AI agent could cause unintended interactions with any active UI, making this high severity.

From the tool's definition "Send keystrokes to an element" — actively triggers browser/UI input actions by injecting keystrokes into interface elements

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs send_keys safely

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

send_keys Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_keys": {
      "limits": [
        {
          "counter": "send_keys_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 Ncp, apply this rule, and every send_keys call is checked against it from then on.

FAQ

Questions about send_keys

What does the send_keys tool do? +

Send keystrokes to an element. It is categorised as a Execute tool in the Ncp 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 Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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