AI agents call taproot_cultivate 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.
The tool performs a query-like comparison of two folders and returns information about unprocessed sources. This is a read-only operation that retrieves and presents data without side effects. The low severity reflects that misuse would only result in viewing incorrect or unnecessary information without impacting the vault.
From the tool's definition Tool description states it 'lists the gap' between sources and notes folders—a comparison and listing operation with no modification. No create, update, delete, or execute operations are mentioned.
Attacks that exploit this kind of access
Use this whenever the user wants to know which raw sources still need processing into the wiki. Compares the sources folder against the notes folder and lists the gap. 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_cultivate: 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_cultivate 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_cultivate 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_cultivate. 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_cultivate 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 →