editor_move_asset · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_move_asset does on Godot

AI agents use editor_move_asset 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.

PARAMETERS

Parameter	Type	Required	Description
`to`	string	Yes
`from`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_move_asset needs a policy

Moving a file changes its location and potentially breaks references within a project, but the operation is reversible (can be moved back). This is Write rather than Destructive because the data itself is not deleted or overwritten. Severity is medium because misuse could break project asset references and require cleanup, but the operation is not irreversible or high-impact by default.

From the tool's definition Tool description states 'Move a file to a new location via editor' — this modifies the filesystem by relocating an asset, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_move_asset Rate-limited

editor_move_asset 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_move_asset": {
      "limits": [
        {
          "counter": "editor_move_asset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_move_asset

What does the editor_move_asset tool do? +

Move a file to a new location via editor. 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.

What parameters does editor_move_asset accept? +

editor_move_asset accepts 2 parameters: to, from. Required: to, from. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_move_asset? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_move_asset: 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.

What risk level is editor_move_asset? +

editor_move_asset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit editor_move_asset? +

Yes. Add a rate_limit block to the editor_move_asset 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.

How do I block editor_move_asset completely? +

Set action: deny in the PolicyLayer policy for editor_move_asset. 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.

What MCP server provides editor_move_asset? +

editor_move_asset is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.