AI agents use move_items to create or update resources in Filesystem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filesystem environment.
Moving and renaming files are write operations that modify metadata and locations but do not destroy data irreversibly. While the blast radius is moderate (could disrupt system organization or break paths), the operation is reversible via another move operation. Severity is medium rather than high because the impact is localized to file organization without data loss or system-level execution.
From the tool's definition Tool description states 'Move or rename multiple specified files/directories' — these are reversible modifications that change file/directory locations and names without deletion.
Documented attack patterns abuse exactly the kind of access move_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem, and nothing reaches the server without passing your rules. This is the rule we recommend for move_items:
{
"version": "1",
"default": "deny",
"tools": {
"move_items": {
"limits": [
{
"counter": "move_items_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_items 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 or rename multiple specified files/directories. It is categorised as a Write tool in the Filesystem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP server in PolicyLayer and add a rule for move_items: 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 Filesystem. Nothing to install.
move_items 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_items 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_items. 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_items is provided by the Filesystem MCP server (sylphxai/filesystem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Filesystem, 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.
13 Filesystem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.