list_obsidian_notes
AI agents call list_obsidian_notes to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations retrieve and enumerate data without side effects. Even with an empty description, the tool name 'list_obsidian_notes' clearly indicates a Read category function. The severity is low because listing notes poses minimal risk if misused—an agent might retrieve unwanted information but cannot alter, delete, or execute code.
From the tool's definition Tool name is 'list_obsidian_notes' which indicates a listing/querying operation. The server description emphasizes 'search' and 'structured context sources,' and this tool fits the pattern of read-only operations alongside destructive (delete_obsidian_note),…
Attacks that exploit this kind of access
list_obsidian_notes. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for list_obsidian_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 MCP Server. Nothing to install.
list_obsidian_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 list_obsidian_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 list_obsidian_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.
list_obsidian_notes is provided by the Obsidian MCP Server MCP server (nbaradar/obsidian-mcp-server). 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 →