input.send_keys
Send a key or chord to the focused window (e.g. enter, tab, ctrl+s, alt+f4, win). Side effect: real key events on the remote desktop. Prefer bundling into input.send_actions when the shortcut follows a click/type in the same planned sequence. Use input.type_text for literal strings, not this tool.
This record as markdown: /tools/com-glasswarp-mcp-server/input.send-keys.md
What input.send_keys does on Glasswarp
AI agents invoke input.send_keys to trigger actions in Glasswarp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
keys | string | Yes | Key or combo, e.g. enter, tab, ctrl+s, alt+f4, win |
session_id | string | Yes | Active session id |
Parameters from the server's own tool schema.
Why input.send_keys is rated High
Sends arbitrary keystrokes to a live Windows desktop, enabling wide-ranging system-level actions.
From the tool's definition real key events on the remote desktop, alt+f4, win
Attacks that exploit this kind of access
The rule that runs input.send_keys safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Glasswarp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For input.send_keys, this is the rule to start with:
input.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.
The button opens the PolicyLayer dashboard: create your workspace, connect Glasswarp, apply this rule, and every input.send_keys call is checked against it from then on.
Questions about input.send_keys
Send a key or chord to the focused window (e.g. enter, tab, ctrl+s, alt+f4, win). Side effect: real key events on the remote desktop. Prefer bundling into input.send_actions when the shortcut follows a click/type in the same planned sequence. Use input.type_text for literal strings, not this tool. It is categorised as a Execute tool in the Glasswarp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
input.send_keys accepts 2 parameters: keys, session_id. Required: keys, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Glasswarp MCP server in PolicyLayer and add a rule for input.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 Glasswarp. Nothing to install.
input.send_keys is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the input.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.
Set action: deny in the PolicyLayer policy for input.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.
input.send_keys is provided by the Glasswarp MCP server (https://mcp.glasswarp.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Glasswarp, and thousands of servers like it.
Across the catalogue