rename_note_tool
A write tool on the Obsidian MCP server.
This record as markdown: /tools/adrienthebo-obsidian-mcp/rename-note-tool.md
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 rename_note_tool is rated Medium
Renaming a note modifies metadata and potentially filesystem references within a vault, which is a Write operation (reversible change). While the description is empty, the server's stated purpose includes 'managing notes' and the presence of similar write-capable tools (create_note_tool, edit_note_section_tool) on the same server indicates this is a content modification tool.
From the tool's definition Tool name is 'rename_note_tool'; sibling tools include 'create_note_tool', 'delete_note_tool', and 'edit_note_section_tool', indicating this server performs content modification operations. Renaming is a reversible modification to note metadata.
Attacks that exploit this kind of access
The rule that runs rename_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 rename_note_tool, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian MCP Server, apply this rule, and every rename_note_tool call is checked against it from then on.
Questions about rename_note_tool
rename_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 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.
rename_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 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.
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.
rename_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