move_file

THE RISK

Medium Risk

Why move_file needs a policy

Moving/renaming files is a Write operation: it modifies file system state reversibly. While the action could break file references or Obsidian links if a user relies on specific file paths, the operation itself is not destructive (data is preserved, not deleted) and not Execute (no code execution).

From the tool's definition Tool description states "Move or rename a file" which modifies file location and name metadata without deletion. The operation is reversible—files can be moved again to restore original state.

Documented attack patterns abuse exactly the kind of access move_file gives an agent:

POLICY

How to control move_file

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian HTTP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for move_file:

policy.json

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

move_file 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.

Create a free account and register Obsidian HTTP MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian HTTP MCP tools

Destructive delete_file Delete a file. By default moves to .trash-http-mcp/ for recovery. Set permanent=true for i Destructive delete_folder Delete all files in a folder recursively. By default moves to .trash-http-mcp/ (soft delet Write create_directory Create a new directory. Idempotent (returns success even if already exists). Does NOT crea Write edit_file Surgically edit file content using exact string replacement (pattern matching). Use this f Write write_file Create or update a file. Use mode=create for new files, mode=overwrite to replace existing Read find_files Search files in vault with fuzzy matching. Use this when you don\ Read get_file_info Get file metadata (size, modification date). Returns exists: false if file not found. Read list_dir List subdirectories in a path. Returns only folder names (not files). IMPORTANT: Path must

All 12 Obsidian HTTP MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about move_file

What does the move_file tool do? +

Move or rename a file. Works for both moving to different folder and renaming in same folder. It is categorised as a Write tool in the Obsidian HTTP MCP 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_file? +

Register the Obsidian HTTP MCP server in PolicyLayer and add a rule for move_file: 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 Obsidian HTTP MCP. Nothing to install.

What risk level is move_file? +

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

Can I rate-limit move_file? +

Yes. Add a rate_limit block to the move_file 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_file completely? +

Set action: deny in the PolicyLayer policy for move_file. 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_file? +

move_file is provided by the Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian HTTP MCP tool call.

Start from Obsidian HTTP MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →