Use this the FIRST time a user wants to set up, configure, or initialize Taproot for their vault. Scans the vault to detect existing structure, conventions, and CLAUDE.md, then returns three options (A: adapt to existing, B: structured knowledge base, C: custom). After the user picks, call \
AI agents call taproot_setup_scan 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 read/scan operation on the vault to detect existing structure and conventions. It does not modify, delete, or create data — it only reads and presents configuration options to the user for a subsequent action. The follow-up configuration step would be a separate tool call.
From the tool's definition Scans the vault to detect existing structure, conventions, and CLAUDE.md, then returns three options
Attacks that exploit this kind of access
Use this the FIRST time a user wants to set up, configure, or initialize Taproot for their vault. Scans the vault to detect existing structure, conventions, and CLAUDE.md, then returns three options (A: adapt to existing, B: structured knowledge base, C: custom). After the user picks, call \. 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_setup_scan: 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_setup_scan 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_setup_scan 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_setup_scan. 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_setup_scan 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 →