MCP Tool: Creates a new note file with optional YAML frontmatter.
AI agents use create_note to create or update resources in Obsidian MCP Tool Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Tool Server environment.
create_note performs a reversible write operation—it creates a new file with optional metadata. This falls squarely into the Write category. Severity is low because: (1) note creation in a personal knowledge management system has minimal blast radius, (2) the operation is easily undone, and (3) there are no side effects beyond vault modification (no code execution, data deletion, or financial impact).
From the tool's definition Tool description states 'Creates a new note file' — a clear create operation that writes new data to the Obsidian vault.
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 Tool Server, 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.
MCP Tool: Creates a new note file with optional YAML frontmatter. It is categorised as a Write tool in the Obsidian MCP Tool Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Tool 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 MCP Tool 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 MCP Tool Server MCP server (rwb3n/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.