Create a new note in the Obsidian vault. Supports nested folder creation.
AI agents use create_note to create or update resources in Obsidian Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Tools MCP Server environment.
The tool creates new data (notes) in a vault system. This is reversible because created notes can be deleted later via the delete_note tool. While it has the potential to clutter a vault or trigger downstream effects through templates, the primary action is data creation without inherent destructiveness.
From the tool's definition Tool description states it creates 'a new note in the Obsidian vault', which is a reversible write operation. The server description mentions 'full CRUD operations' where C (Create) is explicitly write-level.
Attacks that exploit this kind of access
Create a new note in the Obsidian vault. Supports nested folder creation. It is categorised as a Write tool in the Obsidian Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Tools MCP Server MCP server in PolicyLayer and add a rule for create_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 Tools MCP Server. Nothing to install.
create_note 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_note is provided by the Obsidian Tools MCP Server MCP server (sureshsankaran/obsidian-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →