Critical Risk →

edit_note

MCP Tool: Overwrites an existing note with new content, with backup option.

How to control edit_note ↓

AI agents call edit_note to permanently remove resources in Obsidian MCP Tool Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Overwriting a file's content is destructive by default because the original data is lost. The backup option mitigates this only if explicitly invoked, but the tool's primary action is irreversible overwrite. An AI agent misusing this could silently replace any note in the vault with arbitrary content, with potential permanent data loss if no backup is made.

From the tool's definition 'Overwrites an existing note with new content' — the original content is replaced; without backup this is irreversible. The backup is optional ('with backup option'), meaning it may or may not be used.

Documented attack patterns abuse exactly the kind of access edit_note gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Tool Server, and nothing reaches the server without passing your rules. This is the rule we recommend for edit_note:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "edit_note"
  ]
}

edit_note disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Obsidian MCP Tool Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the edit_note tool do? +

MCP Tool: Overwrites an existing note with new content, with backup option. It is categorised as a Destructive tool in the Obsidian MCP Tool Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on edit_note? +

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

What risk level is edit_note? +

edit_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit edit_note? +

Yes. Add a rate_limit block to the edit_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 edit_note completely? +

Set action: deny in the PolicyLayer policy for edit_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 edit_note? +

edit_note is provided by the Obsidian MCP Tool Server MCP server (rwb3n/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian MCP Tool Server tool call.

Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.