Move or rename a note to a new location in the Obsidian vault
AI agents use move_note to create or update resources in Enhanced Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Obsidian MCP Server environment.
Moving or renaming a note is a reversible write operation that modifies metadata and file paths within the vault. While it changes the organizational structure and could affect links/references if not handled by the system, it does not destroy data (hence not Destructive) and is not irreversible in most note-taking systems where undo or version history may apply.
From the tool's definition Tool description states 'Move or rename a note to a new location' which modifies the file system state of the knowledge base without deletion.
Documented attack patterns abuse exactly the kind of access move_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_note:
{
"version": "1",
"default": "deny",
"tools": {
"move_note": {
"limits": [
{
"counter": "move_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_note 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.
Free to start. No card required.
Move or rename a note to a new location in the Obsidian vault. It is categorised as a Write tool in the Enhanced Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Obsidian MCP Server MCP server in PolicyLayer and add a rule for move_note: 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 Enhanced Obsidian MCP Server. Nothing to install.
move_note 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_note 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_note. 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_note is provided by the Enhanced Obsidian MCP Server MCP server (jianruidutong/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Enhanced Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.