move_path

A write tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/move-path.md

WHAT IT DOES

What move_path does on Allcanuse

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.

RISK

Why move_path is rated Medium

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_path safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_path, this is the rule to start with:

move_path Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_path": {
      "limits": [
        {
          "counter": "move_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every move_path call is checked against it from then on.

FAQ

Questions about move_path

What does the move_path tool do? +

move_path is a write tool on the Allcanuse MCP server. 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.

How do I enforce a policy on move_path? +

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.

What risk level is move_path? +

move_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_path? +

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.

How do I block move_path completely? +

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.

What MCP server provides move_path? +

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.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →