rename_note_tool · Obsidian MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_note_tool does on Obsidian MCP Server

AI agents use rename_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 IT NEEDS A POLICY

Why rename_note_tool needs a policy

Renaming a note is a Write operation—it modifies file metadata reversibly without deleting data or executing arbitrary code. Severity is medium because unintended bulk renames could disrupt vault organization and break internal link references, though the effects are recoverable. Confidence is slightly reduced (0.85) due to the empty description, but the tool name is explicit and the server context is clear.

From the tool's definition Tool name 'rename_note_tool' indicates it modifies note metadata (filename/path) within an Obsidian vault. The description is empty, but context from the server description confirms this server manages Obsidian vaults with 'note management' capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_note_tool Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_note_tool": {
      "limits": [
        {
          "counter": "rename_note_tool_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 Server, so you can run agents against it safely.

FAQ

Questions about rename_note_tool

What does the rename_note_tool tool do? +

rename_note_tool. 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_tool? +

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

What risk level is rename_note_tool? +

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

Can I rate-limit rename_note_tool? +

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

How do I block rename_note_tool completely? +

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

What MCP server provides rename_note_tool? +

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