Create a new note in the Obsidian vault
AI agents use create_note to create or update resources in ObsidianReaderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ObsidianReaderMCP environment.
This tool creates new data (a note) in the Obsidian vault, which is a write operation. While the action is reversible (notes can be deleted), it modifies the vault state. Severity is medium rather than low because bulk or malicious note creation could degrade vault usability or consume storage, but the impact is bounded to the vault and reversible.
From the tool's definition Tool description explicitly states "Create a new note in the Obsidian vault". The sibling tools include destructive operations (delete_note) and read operations, confirming this server manages vault content. Creating a note is a reversible write operation.
Attacks that exploit this kind of access
Create a new note in the Obsidian vault. It is categorised as a Write tool in the ObsidianReaderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ObsidianReader 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 ObsidianReaderMCP. 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 ObsidianReader MCP server (qianjue-cn/obsidianreadermcp). 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 →