rename_note

THE RISK

Medium Risk

Why rename_note needs a policy

Renaming a note is a reversible write operation that modifies data (the note's identifier/path) but does not delete it or trigger external financial/code execution effects. The operation can be undone by renaming again.

From the tool's definition Tool name 'rename_note' with description 'Rename a note file' indicates modification of file metadata (the filename/note title) within an Obsidian vault.

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

POLICY

How to control rename_note

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_note": {
      "limits": [
        {
          "counter": "rename_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

rename_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.

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian MCP Server tools

Destructive cleanup_broken_references Remove/fix broken links Destructive delete_attachment Remove attachment file Destructive delete_note Delete a note from the vault Execute execute_dataview_query Run Dataview DQL query and return results Write remove_tags Remove tags from an existing note Write regex_search_and_replace Find and replace with regex across vault Write add_card_to_canvas Add text/note/media card to canvas Write add_connection_to_canvas Connect cards with lines/arrows

All 120 Obsidian MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about rename_note

What does the rename_note tool do? +

Rename a note file. 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.

How do I enforce a policy on rename_note? +

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

What risk level is rename_note? +

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

Can I rate-limit rename_note? +

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

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

rename_note is provided by the Obsidian MCP Server MCP server (kynlos/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 Server tool call.

Start from Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →