Get the most connected notes by link count or PageRank.
AI agents call get_most_connected_notes to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries graph metrics (link count, PageRank) and returns results without modifying vault state, executing commands, or creating obligations. Despite the server's broader capabilities (execute_command, delete_file, patch_content), this specific tool is narrowly scoped to read and analyze existing note relationships.
From the tool's definition Tool description states it 'Get[s] the most connected notes by link count or PageRank' — a pure retrieval operation with no modifications, deletions, or side effects. The verb 'get' indicates data retrieval only.
Attacks that exploit this kind of access
Get the most connected notes by link count or PageRank. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for get_most_connected_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 Modified. Nothing to install.
get_most_connected_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 get_most_connected_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 get_most_connected_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.
get_most_connected_notes is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-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 →