Use this whenever the user wants a synthesized answer drawn from MULTIPLE notes across their vault — a research-style question that needs cross-referencing, citation, and saving the result. Reads the index, locates relevant pages, returns their content so you can synthesize an answer with [[wikil...
AI agents call taproot_harvest to retrieve information from Synapse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
taproot_harvest is a search and retrieval mechanism that queries an Obsidian vault's index and returns note content for synthesis by the user/AI. It has no side effects: it does not create, modify, delete, execute commands, or commit financial transactions. The tool explicitly describes reading and returning data.
From the tool's definition Tool performs 'reads the index, locates relevant pages, returns their content' — pure retrieval with no modification or deletion. The synthesis of results is performed by the AI, not the tool. No write operations, no code execution, no data destruction.
Attacks that exploit this kind of access
Use this whenever the user wants a synthesized answer drawn from MULTIPLE notes across their vault — a research-style question that needs cross-referencing, citation, and saving the result. Reads the index, locates relevant pages, returns their content so you can synthesize an answer with [[wikilink]] citations. Triggers:. It is categorised as a Read tool in the Synapse MCP Server, which means it retrieves data without modifying state.
Register the Synapse MCP server in PolicyLayer and add a rule for taproot_harvest: 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 Synapse. Nothing to install.
taproot_harvest 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 taproot_harvest 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 taproot_harvest. 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.
taproot_harvest is provided by the Synapse MCP server (tomjrworks/synapse-obsidian). 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 →