taproot_sow · Synapse MCP: Risk & Policy

WHAT IT DOES

What taproot_sow does on Synapse

AI agents use taproot_sow 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_sow needs a policy

This tool creates a structured set of files and folders (scaffold) in the user's vault. It writes new content (directories, markdown files, config) but does not delete or overwrite existing data irreversibly, nor does it execute code or involve finances. The blast radius is medium because it could create unwanted directory structures and files across the vault, but these are reversible.

From the tool's definition 'one-call scaffold of a structured knowledge base on a specific topic (sources/, notes/, outputs/, CLAUDE.md, index.md, config)' — creates multiple files and directory structures in the Obsidian vault

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taproot_sow Rate-limited

taproot_sow 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_sow": {
      "limits": [
        {
          "counter": "taproot_sow_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_sow

What does the taproot_sow tool do? +

LEGACY shortcut. Use only when the user wants a one-call scaffold of a structured knowledge base on a specific topic (sources/, notes/, outputs/, CLAUDE.md, index.md, config) and is willing to skip the option-A/B/C choice. For most users, prefer \. 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_sow? +

Register the Synapse MCP server in PolicyLayer and add a rule for taproot_sow: 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_sow? +

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

Can I rate-limit taproot_sow? +

Yes. Add a rate_limit block to the taproot_sow 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_sow completely? +

Set action: deny in the PolicyLayer policy for taproot_sow. 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_sow? +

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