simulate_action
Simulate an input action (from InputMap) being pressed/released
This record as markdown: /tools/keeveeg-godot-mcp/simulate-action.md
What simulate_action does on Godot
AI agents invoke simulate_action 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 | string | Yes | Input action name (e.g. 'ui_accept', 'move_left') |
pressed | boolean | — | Whether pressed (default: true) |
Parameters from the server's own tool schema.
Why simulate_action is rated High
This tool triggers simulated input actions in the Godot engine, which constitutes executing external operations that can affect game state, UI interactions, or other runtime behaviors. It's not merely reading data, but actively causing the engine to process input events whose effects depend on the arguments provided.
From the tool's definition Simulate an input action (from InputMap) being pressed/released
Attacks that exploit this kind of access
The rule that runs simulate_action 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_action, this is the rule to start with:
simulate_action 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_action call is checked against it from then on.
Questions about simulate_action
Simulate an input action (from InputMap) being pressed/released. 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_action accepts 2 parameters: action, pressed. Required: action. 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_action: 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_action 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_action 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_action. 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_action 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