taproot_save_url · Synapse MCP: Risk & Policy

WHAT IT DOES

What taproot_save_url does on Synapse

AI agents use taproot_save_url 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_save_url needs a policy

The tool creates new notes/files in the Obsidian vault by saving URLs and extracted content with frontmatter metadata. This is a Write operation (data creation/modification) rather than Read (it modifies state) or Destructive (changes are reversible, vault can be edited/deleted later).

From the tool's definition Tool description states it 'fetches the URL, extracts text, files it under the configured sources folder' — this creates and stores new data in the user's vault, a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taproot_save_url Rate-limited

taproot_save_url 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_save_url": {
      "limits": [
        {
          "counter": "taproot_save_url_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_save_url

What does the taproot_save_url tool do? +

Use this whenever the user wants to save a URL, article, blog post, web page, or link to their vault. Single call: fetches the URL, extracts text, files it under the configured sources folder (or a folder you suggest) with frontmatter. PREFER this for any URL save. Triggers:. 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_save_url? +

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

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

Can I rate-limit taproot_save_url? +

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

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

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