This record as markdown: /tools/keeveeg-godot-mcp/edit-resource.md
What edit_resource does on Godot
AI agents use edit_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 |
|---|---|---|---|
path | string | Yes | Resource file path (e.g. 'res://assets/theme.tres') |
properties | object | Yes | Properties to set |
Parameters from the server's own tool schema.
Why edit_resource is rated Medium
The tool modifies existing resources by editing their properties, which is a reversible write operation. This is categorized as Write rather than Execute because it changes configuration/properties rather than running code or triggering complex external effects.
From the tool's definition Tool name 'edit_resource' with description 'Edit properties of an existing resource' indicates modification of data. Sibling tools (add_animation_track, add_audio_bus, add_autoload, etc.) consistently show write operations on Godot game engine resources.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs edit_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 edit_resource, this is the rule to start with:
edit_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 edit_resource call is checked against it from then on.
Questions about edit_resource
Edit properties of an existing resource. 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.
edit_resource accepts 2 parameters: path, properties. Required: path, properties. 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 edit_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.
edit_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 edit_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 edit_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.
edit_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