AI agents use tool_move_file to create or update resources in UltimateCoder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UltimateCoder environment.
Moving a file modifies filesystem state reversibly—the source and destination can be swapped to undo the action. This is Write rather than Destructive because the operation is theoretically reversible. Severity is high due to potential for unintended filesystem corruption, data loss (if destination exists and is overwritten), or disruption of application dependencies.
From the tool's definition Tool name 'tool_move_file' indicates file relocation/modification. Server context shows file handling automation on local machine.
Documented attack patterns abuse exactly the kind of access tool_move_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UltimateCoder, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_move_file:
{
"version": "1",
"default": "deny",
"tools": {
"tool_move_file": {
"limits": [
{
"counter": "tool_move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tool_move_file 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.
Free to start. No card required.
tool_move_file. It is categorised as a Write tool in the UltimateCoder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UltimateCoder MCP server in PolicyLayer and add a rule for tool_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 UltimateCoder. Nothing to install.
tool_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 tool_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 tool_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.
tool_move_file is provided by the UltimateCoder MCP server (m-ahmed-elbeskeri/ultimatecodermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UltimateCoder, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 UltimateCoder tools catalogued and risk-classified — across an index of 43,000+ MCP servers.