Read multiple notes with full content and metadata
AI agents call read_notes to retrieve information from Obsidian Ai Curator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries note content from an Obsidian vault without creating, modifying, or deleting data. It has no side effects beyond returning information, making it a Read operation. The severity is low because exposure of this capability allows only information access to the user's own vault, with minimal blast radius unless the vault contains highly sensitive information.
From the tool's definition Tool name 'read_notes' and description 'Read multiple notes with full content and metadata' explicitly indicate data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access read_notes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for read_notes:
{
"version": "1",
"default": "deny",
"tools": {
"read_notes": {}
}
}read_notes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read multiple notes with full content and metadata. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for read_notes: 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 Ai Curator. Nothing to install.
read_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_notes 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 read_notes. 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.
read_notes is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.