This record as markdown: /tools/aapanel-mcp/file-move.md
What file_move does on Aapanel
AI agents use file_move to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why file_move is rated Medium
File move/rename operations modify file system metadata and structure reversibly. While potentially disruptive if misapplied (moving critical system files), the action is theoretically reversible (can be moved back), distinguishing it from destructive deletion.
From the tool's definition Tool name 'file_move' and description 'Move or rename a file/directory' indicate reversible modification of file system state.
Attacks that exploit this kind of access
The rule that runs file_move safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_move, this is the rule to start with:
file_move 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 Aapanel, apply this rule, and every file_move call is checked against it from then on.
Questions about file_move
Move or rename a file/directory. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for file_move: 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 Aapanel. Nothing to install.
file_move 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 file_move 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 file_move. 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.
file_move is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue