Send a special key to the C64 keyboard buffer. For control keys that can
AI agents invoke send_key to trigger actions in Commodore 64 Ultimate Computer 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.
Sending keystrokes to a machine's keyboard buffer triggers actions on the target system — effectively remote input injection that can cause the C64 to execute commands, navigate menus, or interact with running programs. This is an external operation whose effects depend on which key is sent, placing it in the Execute category.
From the tool's definition Send a special key to the C64 keyboard buffer
Documented attack patterns abuse exactly the kind of access send_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Commodore 64 Ultimate Computer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_key:
{
"version": "1",
"default": "deny",
"tools": {
"send_key": {
"limits": [
{
"counter": "send_key_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_key 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.
Free to start. No card required.
Send a special key to the C64 keyboard buffer. For control keys that can. It is categorised as a Execute tool in the Commodore 64 Ultimate Computer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Commodore 64 Ultimate Computer MCP Server MCP server in PolicyLayer and add a rule for send_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 Commodore 64 Ultimate Computer MCP Server. Nothing to install.
send_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 send_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 send_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.
send_key is provided by the Commodore 64 Ultimate Computer MCP Server MCP server (xphileby/c64u-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Commodore 64 Ultimate Computer MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
54 Commodore 64 Ultimate Computer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.