start_recording
🔴 Game must be running. Start recording game state changes
This record as markdown: /tools/keeveeg-godot-mcp/start-recording.md
What start_recording does on Godot
AI agents invoke start_recording 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 start_recording is rated High
This tool executes an operation that initiates a recording process on a running Godot game. While recording itself is not inherently destructive, it is an Execute category action because it triggers an external operation with side effects (creating recording artifacts, consuming resources, potentially capturing sensitive game state data).
From the tool's definition Tool description states 'Start recording game state changes' which triggers an external operation (recording) on a running game instance.
Attacks that exploit this kind of access
The rule that runs start_recording 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 start_recording, this is the rule to start with:
start_recording 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 start_recording call is checked against it from then on.
Questions about start_recording
🔴 Game must be running. Start recording game state changes. 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 start_recording: 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.
start_recording 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 start_recording 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 start_recording. 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.
start_recording 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