bundle_dependencies

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/bundle-dependencies.md

WHAT IT DOES

What bundle_dependencies does on tdmcp — TouchDesigner MCP server

AI agents use bundle_dependencies 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.

RISK

Why bundle_dependencies is rated Medium

bundle_dependencies performs multiple write operations: it copies files to disk, rewrites parameters in the live network to update paths, and saves a .tox file. These are all reversible modifications (files can be deleted, parameters changed back, tox regenerated). The tool does not execute arbitrary code, delete irreversibly, or move money.

From the tool's definition "COPY each existing asset into <out_dir>/assets/", "rewrite each referencing parameter in the LIVE network to the copied relative path", "then save the COMP as a .tox". The tool creates new files, modifies network parameters, and saves data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bundle_dependencies 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 bundle_dependencies, this is the rule to start with:

bundle_dependencies Rate-limited

bundle_dependencies 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": {
    "bundle_dependencies": {
      "limits": [
        {
          "counter": "bundle_dependencies_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every bundle_dependencies call is checked against it from then on.

FAQ

Questions about bundle_dependencies

What does the bundle_dependencies tool do? +

Make a COMP self-contained: recursively scan its subtree for external file references (movie/image files, fonts, LUTs, externaltox links — reusing the collect_project_assets scan), COPY each existing asset into <out_dir>/assets/, rewrite each referencing parameter in the LIVE network to the copied relative path (assets/<file>), then save the COMP as a .tox beside its assets with a tdmcp-component manifest. The result is a folder you can move to another machine and open without broken links. Delta vs make_portable_tox (which saves the .tox only, leaving external assets behind) and collect_project_assets (which only reports refs). Rewriting mutates the live network — set rewrite_refs=false to copy-and-report without touching parameters. 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.

How do I enforce a policy on bundle_dependencies? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for bundle_dependencies: 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.

What risk level is bundle_dependencies? +

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

Can I rate-limit bundle_dependencies? +

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

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

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

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 507 tdmcp — TouchDesigner MCP server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →