stop_recording
🔴 Game must be running. Stop recording and return the recorded game state data
This record as markdown: /tools/keeveeg-godot-mcp/stop-recording.md
What stop_recording does on Godot
AI agents invoke stop_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 stop_recording is rated High
This tool stops an active recording process and retrieves the resulting data. It triggers an external operation (stopping a recording session in a running game) with side effects beyond simple data retrieval. It's not purely Read since it terminates an ongoing process, and not Destructive since data is returned rather than deleted. Execute best fits an action that controls an external runtime operation.
From the tool's definition Stop recording and return the recorded game state data
Attacks that exploit this kind of access
The rule that runs stop_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 stop_recording, this is the rule to start with:
stop_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 stop_recording call is checked against it from then on.
Questions about stop_recording
🔴 Game must be running. Stop recording and return the recorded game state data. 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 stop_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.
stop_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 stop_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 stop_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.
stop_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