taproot_water · Synapse MCP: Risk & Policy

WHAT IT DOES

What taproot_water does on Synapse

AI agents use taproot_water 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_water needs a policy

This tool processes an existing file and creates or modifies structured pages with wikilinks in the Obsidian vault. It is a write/transform operation — it creates new content (concept/entity pages) from an existing source. It is reversible in principle (pages could be deleted), so Write is more appropriate than Destructive.

From the tool's definition 're-process or deeply ingest an EXISTING source file at a known path into structured concept/entity pages with wikilinks'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taproot_water Rate-limited

taproot_water 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_water": {
      "limits": [
        {
          "counter": "taproot_water_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_water

What does the taproot_water tool do? +

FALLBACK for the multi-step ingestion pipeline. Use only when the user explicitly wants to re-process or deeply ingest an EXISTING source file at a known path into structured concept/entity pages with wikilinks. For. 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_water? +

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

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

Can I rate-limit taproot_water? +

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

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

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