simulate_sequence
Simulate a sequence of input events with timing
This record as markdown: /tools/keeveeg-godot-mcp/simulate-sequence.md
What simulate_sequence does on Godot
AI agents invoke simulate_sequence 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 |
|---|---|---|---|
events | array | Yes | Sequence of input events to simulate |
Parameters from the server's own tool schema.
Why simulate_sequence is rated High
This tool triggers a sequence of input events within the Godot engine, which constitutes executing external operations (simulated user/input actions) with timing control. It is not merely reading or writing data; it actively drives engine behavior, making Execute the appropriate category. Misuse could trigger unintended in-game or editor actions, warranting medium severity.
From the tool's definition simulate_sequence — 'Simulate a sequence of input events with timing'
Attacks that exploit this kind of access
The rule that runs simulate_sequence 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_sequence, this is the rule to start with:
simulate_sequence 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_sequence call is checked against it from then on.
Questions about simulate_sequence
Simulate a sequence of input events with timing. 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_sequence accepts 1 parameter: events. Required: events. 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_sequence: 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_sequence 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_sequence 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_sequence. 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_sequence 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