Move · Nexus MCP for Obsidian MCP: Risk & Policy

WHAT IT DOES

What Move does on Nexus MCP for Obsidian

AI agents use Move to create or update resources in Nexus MCP for Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus MCP for Obsidian environment.

WHY IT NEEDS A POLICY

Why Move needs a policy

Moving or renaming files changes their location and identity within the vault structure, which is a reversible write operation. While this could affect references or links within notes, the action is non-destructive (files are not deleted, merely relocated) and can be undone. This is less severe than Destructive (which would involve deletion) but more impactful than Read operations.

From the tool's definition Tool description states 'Move or rename a file or folder' — these are reversible modifications to file/folder metadata and location within the vault.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Move Rate-limited

Move 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": {
      "limits": [
        {
          "counter": "move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nexus MCP for Obsidian, so you can run agents against it safely.

FAQ

Questions about Move

What does the Move tool do? +

Move or rename a file or folder. It is categorised as a Write tool in the Nexus MCP for Obsidian 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? +

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

What risk level is Move? +

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

Can I rate-limit Move? +

Yes. Add a rate_limit block to the 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.

How do I block Move completely? +

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

What MCP server provides Move? +

Move is provided by the Nexus MCP for Obsidian MCP server (profsynapse/nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.