add_resource
Add a resource (material, texture, etc.) to a node property
This record as markdown: /tools/keeveeg-godot-mcp/add-resource.md
What add_resource does on Godot
AI agents use add_resource 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 |
|---|---|---|---|
node_path | string | Yes | Node to add resource to (e.g. 'Player' or 'Player/Cube') |
properties | object | — | Optional property key-value pairs |
resource_type | string | Yes | Resource type (e.g. 'Material', 'Texture2D') |
Parameters from the server's own tool schema.
Why add_resource is rated Medium
This tool creates or modifies project assets by adding resources to node properties. This is a reversible write operation typical of game engine resource management. Severity is medium because misuse could clutter or corrupt a project's resource structure, but changes are generally reversible through undo or deletion.
From the tool's definition Tool name 'add_resource' and description 'Add a resource (material, texture, etc.) to a node property' indicate creation/modification of project resources.
Attacks that exploit this kind of access
The rule that runs add_resource 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 add_resource, this is the rule to start with:
add_resource 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 add_resource call is checked against it from then on.
Questions about add_resource
Add a resource (material, texture, etc.) to a node property. 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.
add_resource accepts 3 parameters: node_path, properties, resource_type. Required: node_path, resource_type. 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 add_resource: 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.
add_resource 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 add_resource 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 add_resource. 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.
add_resource 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