move_note_tool
A write tool on the Obsidian MCP server.
This record as markdown: /tools/adrienthebo-obsidian-mcp/move-note-tool.md
What move_note_tool does on Obsidian MCP Server
AI agents use move_note_tool to create or update resources in Obsidian MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
Why move_note_tool is rated Medium
Moving a note changes its filesystem path/location within the vault, modifying the structure reversibly. This is a Write operation with medium severity because it could disrupt a user's vault organization or break relative links if not handled carefully, but the action is undoable.
From the tool's definition Tool name 'move_note_tool' indicates it relocates/reorganizes notes. Description is empty, but sibling tools include 'create_note_tool', 'delete_note_tool', 'edit_note_section_tool', and 'batch_update_properties_tool'—all Write/Destructive operations on vault…
Attacks that exploit this kind of access
The rule that runs move_note_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_note_tool, this is the rule to start with:
move_note_tool 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian MCP Server, apply this rule, and every move_note_tool call is checked against it from then on.
Questions about move_note_tool
move_note_tool is a write tool on the Obsidian MCP Server MCP server. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for move_note_tool: 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 MCP Server. Nothing to install.
move_note_tool 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_tool 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_tool. 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_tool is provided by the Obsidian MCP Server MCP server (adrienthebo/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian MCP Server, and thousands of servers like it.
This server
Across the catalogue