Create a new markdown note at the given path with body content and optional YAML frontmatter. Fails (does not overwrite) if a note already exists at that path — use append_to_note, prepend_to_note, or update_frontmatter for existing notes. Missing directories are created automatically, and a .md ...
AI agents use create_note to create or update resources in Obsidian Mcp Pro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Mcp Pro environment.
This tool creates new notes in an Obsidian vault, which is a reversible write operation. It does not execute code, delete data, or move money. The tool deliberately prevents overwrites and is limited to markdown note creation, making it a straightforward Write action with low severity since the effects are easily reversible (the note can be deleted).
From the tool's definition Tool description explicitly states it 'Create a new markdown note' with 'body content and optional YAML frontmatter' and 'Fails (does not overwrite) if a note already exists'. This is a creation operation that modifies the vault by adding new data.
Documented attack patterns abuse exactly the kind of access create_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for create_note:
{
"version": "1",
"default": "deny",
"tools": {
"create_note": {
"limits": [
{
"counter": "create_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create a new markdown note at the given path with body content and optional YAML frontmatter. Fails (does not overwrite) if a note already exists at that path — use append_to_note, prepend_to_note, or update_frontmatter for existing notes. Missing directories are created automatically, and a .md extension is appended if omitted. It is categorised as a Write tool in the Obsidian Mcp Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Mcp Pro 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 Mcp Pro. 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 Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.