Send a sequence of key steps with optional per-step delays. Useful for complex keyboard operations.
AI agents invoke send_key_sequence to trigger actions in Mcp Serial Hid Kvm. 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.
This tool sends keyboard input sequences to a physical PC via a KVM server. It can trigger arbitrary operations on the remote system (launching applications, entering commands, modifying files, etc.) depending on the key sequences sent. The effect is entirely dependent on the context and arguments, making it Execute.
From the tool's definition Send a sequence of key steps with optional per-step delays. Useful for complex keyboard operations.
Attacks that exploit this kind of access
Send a sequence of key steps with optional per-step delays. Useful for complex keyboard operations. It is categorised as a Execute tool in the Mcp Serial Hid Kvm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Serial Hid Kvm MCP server in PolicyLayer and add a rule for send_key_sequence: 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 Mcp Serial Hid Kvm. Nothing to install.
send_key_sequence 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 send_key_sequence 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 send_key_sequence. 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.
send_key_sequence is provided by the Mcp Serial Hid Kvm MCP server (sunasaji/mcp-serial-hid-kvm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →