keyboard_type · Windows MCP Server MCP: Risk & Policy

WHAT IT DOES

What keyboard_type does on Windows MCP Server

AI agents invoke keyboard_type to trigger actions in Windows 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 keyboard_type needs a policy

Typing text via keyboard is an execution action that sends input to whatever application or UI element is currently focused. In the context of an enterprise automation server controlling Windows PCs, this can type into terminals, browsers, dialogs, or any other application. An AI agent could misuse this to enter commands, credentials, or malicious input into active windows, making it a high-severity Execute action.

From the tool's definition 'Type text using the keyboard' — triggers keyboard input actions on the Windows system, which can interact with any active application or UI element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

keyboard_type Rate-limited

keyboard_type 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": {
    "keyboard_type": {
      "limits": [
        {
          "counter": "keyboard_type_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 Windows MCP Server, so you can run agents against it safely.

FAQ

Questions about keyboard_type

What does the keyboard_type tool do? +

Type text using the keyboard. It is categorised as a Execute tool in the Windows 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 keyboard_type? +

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

What risk level is keyboard_type? +

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

Can I rate-limit keyboard_type? +

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

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

keyboard_type is provided by the Windows MCP Server MCP server (romeo2badboy-rgb/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.