simulate_key
Simulate a keyboard key press/release in the running game
This record as markdown: /tools/keeveeg-godot-mcp/simulate-key.md
What simulate_key does on Godot
AI agents invoke simulate_key to trigger actions in Godot. 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 |
|---|---|---|---|
echo | boolean | — | Whether this is an echo/repeat event |
keycode | string | Yes | Key code name (e.g. 'KEY_ENTER', 'KEY_SPACE', 'KEY_A') |
pressed | boolean | — | Whether pressed (default: true) |
Parameters from the server's own tool schema.
Why simulate_key is rated High
This tool triggers external operations (keyboard input simulation) in a running game process. It executes actions whose effects depend on what key is pressed and the game's current state, potentially triggering any in-game action, menu, command, or shortcut. This qualifies as Execute rather than Write because it drives real-time interactive behavior in an external running process.
From the tool's definition Simulate a keyboard key press/release in the running game
Attacks that exploit this kind of access
The rule that runs simulate_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For simulate_key, this is the rule to start with:
simulate_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every simulate_key call is checked against it from then on.
Questions about simulate_key
Simulate a keyboard key press/release in the running game. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
simulate_key accepts 3 parameters: echo, keycode, pressed. Required: keycode. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for simulate_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 Godot. Nothing to install.
simulate_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 simulate_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 simulate_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.
simulate_key is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
Across the catalogue