taproot_plant · Synapse MCP: Risk & Policy

WHAT IT DOES

What taproot_plant does on Synapse

AI agents use taproot_plant to create or update resources in Synapse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Synapse environment.

WHY IT NEEDS A POLICY

Why taproot_plant needs a policy

This tool sets up and configures a knowledge management system within the user's Obsidian vault. While it performs initial scanning (Read-like), its primary purpose is initialization and configuration of the vault structure, which constitutes reversible data modification (Write). It does not execute arbitrary code, delete data, or move money.

From the tool's definition Tool description states 'set up, configure, or initialize Taproot' and 'Scans the vault to detect existing structure' then 'returns three options' for user selection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taproot_plant Rate-limited

taproot_plant stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "taproot_plant": {
      "limits": [
        {
          "counter": "taproot_plant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Synapse, so you can run agents against it safely.

FAQ

Questions about taproot_plant

What does the taproot_plant tool do? +

[deprecated — use taproot_setup_scan; this alias remains for clients paired before the rename] 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 Write tool in the Synapse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on taproot_plant? +

Register the Synapse MCP server in PolicyLayer and add a rule for taproot_plant: 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.

What risk level is taproot_plant? +

taproot_plant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit taproot_plant? +

Yes. Add a rate_limit block to the taproot_plant 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.

How do I block taproot_plant completely? +

Set action: deny in the PolicyLayer policy for taproot_plant. 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.

What MCP server provides taproot_plant? +

taproot_plant 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.