runtime_input
Inject a key input event into the running game.
This record as markdown: /tools/yanhuifair-godot-mcp/runtime-input.md
What runtime_input does on Godot
AI agents invoke runtime_input 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 |
|---|---|---|---|
action | object | — | "press" or "release". |
keycode | integer | Yes | Godot keycode (e.g. KEY_W=87, KEY_SPACE=32). See https://docs.godotengine.org/en/stable/classes/class_@globals.html#enum-keymodifierkeycode |
Parameters from the server's own tool schema.
Why runtime_input is rated High
Injects input events into a running game process, triggering external execution effects.
From the tool's definition Inject a key input event into the running game
Attacks that exploit this kind of access
The rule that runs runtime_input 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 runtime_input, this is the rule to start with:
runtime_input 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 runtime_input call is checked against it from then on.
Questions about runtime_input
Inject a key input event into 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.
runtime_input accepts 2 parameters: action, keycode. 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 runtime_input: 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.
runtime_input 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 runtime_input 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 runtime_input. 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.
runtime_input is provided by the Godot MCP server (@yanhuifair/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