install_library_package
Install a local tdmcp component package folder, .zip, .tox, or manifest into an explicit project/user package scope, or preserve the legacy dest_dir/<packageName> form. Project scope requires project_dir and uses <project_dir>/.tdmcp/packages. Use inspect_component_manifest first for unknown pack...
This record as markdown: /tools/io-github-pantani-tdmcp/install-library-package.md
What install_library_package does on tdmcp — TouchDesigner MCP server
AI agents use install_library_package 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 install_library_package is rated Medium
The tool installs packages by copying/extracting files into project directories, which is a reversible modification operation (files can be removed or replaced). It does not delete data irreversibly, execute arbitrary code, or move money.
From the tool's definition Tool performs file operations that modify a TouchDesigner project: 'Install a local tdmcp component package folder, .zip, .tox, or manifest', 'This copies or extracts files', 'refuses replacement unless overwrite=true'.
Attacks that exploit this kind of access
The rule that runs install_library_package 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 install_library_package, this is the rule to start with:
install_library_package 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 install_library_package call is checked against it from then on.
Questions about install_library_package
Install a local tdmcp component package folder, .zip, .tox, or manifest into an explicit project/user package scope, or preserve the legacy dest_dir/<packageName> form. Project scope requires project_dir and uses <project_dir>/.tdmcp/packages. Use inspect_component_manifest first for unknown packages. This copies or extracts files, refuses replacement unless overwrite=true, rejects symlinked directory trees, and returns scope plus resolved paths. 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 install_library_package: 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.
install_library_package 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 install_library_package 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 install_library_package. 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.
install_library_package 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