find_orphaned_notes_tool
AI agents call find_orphaned_notes_tool 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.
This tool searches for orphaned notes (notes without incoming links) in an Obsidian vault. It retrieves information about vault state without modifying, deleting, or executing code. The operation is a query/search with no side effects, making it a Read category tool. Severity is low because finding orphaned notes poses minimal risk—it cannot modify user data or trigger external actions.
From the tool's definition Tool name 'find_orphaned_notes_tool' indicates a search/discovery operation to identify notes with no backlinks.
Attacks that exploit this kind of access
find_orphaned_notes_tool. 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 find_orphaned_notes_tool: 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.
find_orphaned_notes_tool 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 find_orphaned_notes_tool 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 find_orphaned_notes_tool. 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.
find_orphaned_notes_tool is provided by the Obsidian MCP Server MCP server (suhailnajeeb/obsidian-mcp). 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 →