Move or rename a file in the vault
AI agents use move to create or update resources in Obsidian Local — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Local environment.
Moving or renaming files modifies the vault's structure and the locations of notes reversibly. While not irreversible, this is more impactful than simple data creation (Write category). It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial operations.
From the tool's definition Tool name 'move' and description 'Move or rename a file in the vault' indicate file modification operations that change file locations and names within the Obsidian vault.
Attacks that exploit this kind of access
Move or rename a file in the vault. It is categorised as a Write tool in the Obsidian Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Local 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 Obsidian Local. Nothing to install.
move 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 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. 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 is provided by the Obsidian Local MCP server (matthewsuazo/obsidian-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →