continue_execution
Continue execution when paused at a breakpoint
This record as markdown: /tools/keeveeg-godot-mcp/continue-execution.md
What continue_execution does on Godot
AI agents invoke continue_execution 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.
Why continue_execution is rated High
This tool controls the execution flow of a Godot debugger/runtime session. Continuing execution from a breakpoint is an Execute-category action: it directly triggers code to run in the engine. Misuse could allow bypassing debug checks or advancing through sensitive execution states unexpectedly. Severity is high because it affects a running game/engine process.
From the tool's definition continue_execution — resumes execution when paused at a breakpoint
Attacks that exploit this kind of access
The rule that runs continue_execution 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 continue_execution, this is the rule to start with:
continue_execution 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 continue_execution call is checked against it from then on.
Questions about continue_execution
Continue execution when paused at a breakpoint. 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.
Register the Godot MCP server in PolicyLayer and add a rule for continue_execution: 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.
continue_execution 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 continue_execution 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 continue_execution. 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.
continue_execution 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