move_note | PolicyLayer

WHAT IT DOES

What move_note does on Obsidian MCP (pgvector + Ollama, self-hosted)

AI agents use move_note to create or update resources in Obsidian MCP (pgvector + Ollama, self-hosted) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP (pgvector + Ollama, self-hosted) environment.

WHY IT NEEDS A POLICY

Why move_note needs a policy

Moving a note is a reversible modification operation (Write category) rather than destructive deletion. It reorganizes vault structure but does not irreversibly delete data. Severity is medium because unintended moves could disrupt vault organization and wikilink graph traversal, but the operation is undoable.

From the tool's definition Tool name 'move_note' indicates relocation of a note within the vault structure. Sibling tools include 'create_note', 'delete_note', 'edit_note', confirming this server handles note CRUD operations. Description is empty, reducing specificity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_note Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_note": {
      "limits": [
        {
          "counter": "move_note_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 Obsidian MCP (pgvector + Ollama, self-hosted), so you can run agents against it safely.

FAQ

Questions about move_note

What does the move_note tool do? +

move_note. It is categorised as a Write tool in the Obsidian MCP (pgvector + Ollama, self-hosted) 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_note? +

Register the Obsidian MCP (pgvector + Ollama, self-hosted) 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 Obsidian MCP (pgvector + Ollama, self-hosted). Nothing to install.

What risk level is move_note? +

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

Can I rate-limit move_note? +

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.

How do I block move_note completely? +

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.

What MCP server provides move_note? +

move_note is provided by the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server (maxkuminov/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.