Detect communities/clusters of related notes using graph analysis.
AI agents call detect_note_clusters 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 performs graph analysis on notes to identify related clusters. It retrieves and analyzes data (the note relationships and structure) but does not create, modify, delete, or execute any operations. No side effects occur — it only computes and returns clustering results based on existing note data. This is a Read operation.
From the tool's definition Tool name 'detect_note_clusters' and description 'Detect communities/clusters of related notes using graph analysis' — performs analysis on existing note relationships without modification, deletion, or external execution.
Attacks that exploit this kind of access
Detect communities/clusters of related notes using graph analysis. 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 detect_note_clusters: 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.
detect_note_clusters 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 detect_note_clusters 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 detect_note_clusters. 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.
detect_note_clusters 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 →