Send a key or key combination to the remote machine. Use JavaScript key codes (e.g., KeyA, Enter, ControlLeft).
AI agents invoke pikvm_key to trigger actions in PiKVM 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.
This tool sends keyboard input to a physical machine via PiKVM. Keystrokes can trigger arbitrary actions on the remote system — launching applications, executing commands, modifying files, or even destructive operations — depending on what keys are sent. The blast radius is high because an AI agent could use this to type commands into a terminal or interact with any running application on the physical machine.
From the tool's definition "Send a key or key combination to the remote machine" with "full keyboard, mouse, and screen control of a physical machine"
Attacks that exploit this kind of access
Send a key or key combination to the remote machine. Use JavaScript key codes (e.g., KeyA, Enter, ControlLeft). It is categorised as a Execute tool in the PiKVM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PiKVM MCP Server MCP server in PolicyLayer and add a rule for pikvm_key: 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 PiKVM MCP Server. Nothing to install.
pikvm_key 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 pikvm_key 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 pikvm_key. 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.
pikvm_key is provided by the PiKVM MCP Server MCP server (kultivatorconsulting/pikvm_mcp_server). 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 →