This record as markdown: /tools/keeveeg-godot-mcp/uninstall-addon.md
What uninstall_addon does on Godot
AI agents call uninstall_addon to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Addon name to uninstall |
Parameters from the server's own tool schema.
Why uninstall_addon is rated Critical
This tool removes files from the system as part of uninstalling an addon. File deletion is irreversible and cannot be undone, making it a Destructive operation. While the blast radius is somewhat constrained to addon files within a Godot project (not system-wide), the permanent removal of data and potential disruption to the project justify a 'high' severity rating.
From the tool's definition Tool name 'uninstall_addon' combined with description 'Uninstall an addon and remove its files' explicitly indicates irreversible deletion of files.
Attacks that exploit this kind of access
The rule that runs uninstall_addon 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 uninstall_addon, this is the rule to start with:
uninstall_addon is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every uninstall_addon call is checked against it from then on.
Questions about uninstall_addon
Uninstall an addon and remove its files. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
uninstall_addon accepts 1 parameter: name. Required: name. 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 uninstall_addon: 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.
uninstall_addon is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the uninstall_addon 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 uninstall_addon. 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.
uninstall_addon 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