filesystem_move
Move or rename a file or directory within the project (carrying its .import sidecar), then rescan. DESTRUCTIVE (moves on disk; does NOT remap references in other resources) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/filesystem-move.md
What filesystem_move does on Breakpoint
AI agents call filesystem_move to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Destination res:// path |
from_path | string | Yes | Source res:// path (file or directory) |
Parameters from the server's own tool schema.
Why filesystem_move is rated Critical
The tool moves or renames files on disk, which is an irreversible filesystem operation. The description explicitly labels it DESTRUCTIVE and notes it does not remap references in other resources, meaning it can break project references.
From the tool's definition DESTRUCTIVE (moves on disk; does NOT remap references in other resources) — gated by confirmation
Attacks that exploit this kind of access
The rule that runs filesystem_move safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filesystem_move, this is the rule to start with:
filesystem_move is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every filesystem_move call is checked against it from then on.
Questions about filesystem_move
Move or rename a file or directory within the project (carrying its .import sidecar), then rescan. DESTRUCTIVE (moves on disk; does NOT remap references in other resources) — gated by confirmation. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
filesystem_move accepts 3 parameters: confirm, to_path, from_path. Required: to_path, from_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for filesystem_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 Breakpoint. Nothing to install.
filesystem_move is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the filesystem_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 filesystem_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.
filesystem_move is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue