AI agents use move_file 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 |
|---|---|---|---|
source | string | Yes | Source file path (relative to project root) |
destination | string | Yes | Destination file path (relative to project root) |
Parameters from the server's own tool schema.
Moving or renaming a file is a reversible write operation—the file content is preserved, only its location or name changes. This is distinct from deletion (Destructive) or execution (Execute). While it modifies the project structure, the change can be undone by moving/renaming back. Severity is medium because misuse could disrupt project organization or break references, but no permanent data loss occurs.
From the tool's definition Tool name 'move_file' and description 'Move/rename a file within project' indicates file system modification operations that create new state (moved/renamed files) while preserving the original data.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
Move/rename a file within project. 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.
move_file accepts 2 parameters: source, destination. Required: source, destination. 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 move_file: 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.
move_file 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 move_file 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 move_file. 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.
move_file 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.
move_file is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →