Move/rename a file or directory. For multiple operations, use batch_move_files.
AI agents use move_file to create or update resources in OODA Computer Control — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OODA Computer Control environment.
Moving or renaming files modifies the filesystem state reversibly. While the operation changes file metadata and location, it does not permanently destroy data (unlike delete/destructive operations) and does not execute arbitrary code. The blast radius is medium because incorrect moves could temporarily disrupt system operations or application functionality, but the changes can be undone by moving files back.
From the tool's definition Tool description states 'Move/rename a file or directory' - these are reversible file modifications that change file location/name but do not delete data.
Documented attack patterns abuse exactly the kind of access move_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for move_file:
{
"version": "1",
"default": "deny",
"tools": {
"move_file": {
"limits": [
{
"counter": "move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Move/rename a file or directory. For multiple operations, use batch_move_files. It is categorised as a Write tool in the OODA Computer Control MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OODA Computer Control 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 OODA Computer Control. 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 OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.