AI agents use move_path to create or update resources in Allcanuse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allcanuse environment.
Move operations modify file system state by changing file locations and directory structures. This is reversible (can be moved back), making it Write rather than Destructive. Without explicit description, confidence is reduced.
From the tool's definition Tool name 'move_path' indicates file/path movement operations (mv/move commands). The server description mentions 'file editing' and 'systematically manage local systems' with command execution capabilities.
Documented attack patterns abuse exactly the kind of access move_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for move_path:
{
"version": "1",
"default": "deny",
"tools": {
"move_path": {
"limits": [
{
"counter": "move_path_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_path 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_path. It is categorised as a Write tool in the Allcanuse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Allcanuse MCP server in PolicyLayer and add a rule for move_path: 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 Allcanuse. Nothing to install.
move_path 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_path 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_path. 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_path is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, 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.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.