install_library_package
Install a local package folder, zip, tox, or manifest into a local tdmcp package directory.
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 invoke install_library_package to trigger actions in tdmcp — TouchDesigner MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why install_library_package is rated High
Installing packages involves executing installation operations that place files into the system, potentially introducing arbitrary code (shaders, scripts, TOX components) into the TouchDesigner environment. While it is a write-like operation, it triggers external operations whose effects depend on arguments (what package is installed), and installed packages may execute code within TouchDesigner.
From the tool's definition 'Install a local package folder, zip, tox, or manifest into a local tdmcp package directory'
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 rate-capped: a runaway agent can't fire it dozens of times 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 package folder, zip, tox, or manifest into a local tdmcp package directory. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
Across the catalogue