merge_vaults
Merge the contents of a source Obsidian vault into a target vault (defaulting to TDMCP_VAULT_PATH).
This record as markdown: /tools/io-github-pantani-tdmcp/merge-vaults.md
What merge_vaults does on tdmcp — TouchDesigner MCP server
AI agents use merge_vaults to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why merge_vaults is rated Medium
This tool modifies data in the target vault by merging source content into it. While it does not permanently delete data (which would be Destructive), it irreversibly changes the state of the target vault by adding/updating vault contents.
From the tool's definition Tool description states 'Merge the contents of a source Obsidian vault into a target vault', which involves modifying the target vault by combining data from a source vault.
Attacks that exploit this kind of access
The rule that runs merge_vaults safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For merge_vaults, this is the rule to start with:
merge_vaults 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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every merge_vaults call is checked against it from then on.
Questions about merge_vaults
Merge the contents of a source Obsidian vault into a target vault (defaulting to TDMCP_VAULT_PATH). It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for merge_vaults: 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 tdmcp — TouchDesigner MCP server. Nothing to install.
merge_vaults is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_vaults 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 merge_vaults. 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.
merge_vaults is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue