force_garbage_collection
Force garbage collection and report the amount of memory freed
This record as markdown: /tools/keeveeg-godot-mcp/force-garbage-collection.md
What force_garbage_collection does on Godot
AI agents invoke force_garbage_collection 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 force_garbage_collection is rated High
This tool triggers a runtime operation (forcing garbage collection) in the Godot engine. It executes an internal engine process rather than simply reading data or writing/deleting user data. While it doesn't directly delete user-defined data, it forces memory management operations that could affect running state.
From the tool's definition Force garbage collection and report the amount of memory freed
Attacks that exploit this kind of access
The rule that runs force_garbage_collection 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 force_garbage_collection, this is the rule to start with:
force_garbage_collection 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 force_garbage_collection call is checked against it from then on.
Questions about force_garbage_collection
Force garbage collection and report the amount of memory freed. 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 force_garbage_collection: 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.
force_garbage_collection 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 force_garbage_collection 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 force_garbage_collection. 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.
force_garbage_collection 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