install_addon
Install an addon from the Asset Library, git repository, or local path
This record as markdown: /tools/keeveeg-godot-mcp/install-addon.md
What install_addon does on Godot
AI agents use install_addon to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | Git URL or local path (required for git/local sources) |
name | string | Yes | Addon name or identifier |
source | string | — | Installation source (default: asset_lib) |
Parameters from the server's own tool schema.
Why install_addon is rated Medium
Installing an addon creates new files and modifies the project structure reversibly. While it could be argued as Execute (since addon installation may trigger code), the primary action is creation/addition of project resources rather than triggering arbitrary runtime operations.
From the tool's definition Tool installs an addon from external sources (Asset Library, git repository, or local path), which creates/adds new code and resources to a Godot project.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs install_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 install_addon, this is the rule to start with:
install_addon stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 install_addon call is checked against it from then on.
Questions about install_addon
Install an addon from the Asset Library, git repository, or local path. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
install_addon accepts 3 parameters: url, name, source. 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 install_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.
install_addon is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the install_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 install_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.
install_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.
This server
Across the catalogue