validate_library_asset
Check that a local library asset exists and is referenced by an optional manifest. The default static mode preserves the cheap filesystem check. Opt-in deep_roundtrip validates an absolute .tox in an authenticated disposable quarantine bridge on a non-9980 port, using a structured loadTox-only jo...
This record as markdown: /tools/io-github-pantani-tdmcp/validate-library-asset.md
What validate_library_asset does on tdmcp — TouchDesigner MCP server
AI agents call validate_library_asset to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why validate_library_asset is rated Low
This tool reads and verifies the state of existing assets and manifests without modifying, creating, or deleting data. The deep_roundtrip mode loads assets in an isolated quarantine environment for validation only, with no side effects. The explicit mention of 'loadTox-only' and 'verified scratch cleanup' confirms that the operation is entirely non-destructive and read-oriented.
From the tool's definition The tool performs a 'filesystem check' and validation of a library asset existence and manifest reference. The description emphasizes checking (validate), preserving 'cheap filesystem check', and validation modes that do not modify state.
Attacks that exploit this kind of access
The rule that runs validate_library_asset 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 validate_library_asset, this is the rule to start with:
validate_library_asset is read-only, so it stays allowed. 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 validate_library_asset call is checked against it from then on.
Questions about validate_library_asset
Check that a local library asset exists and is referenced by an optional manifest. The default static mode preserves the cheap filesystem check. Opt-in deep_roundtrip validates an absolute .tox in an authenticated disposable quarantine bridge on a non-9980 port, using a structured loadTox-only job with bounded polling and verified scratch cleanup; offline evidence is UNVERIFIED, never PASS. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for validate_library_asset: 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.
validate_library_asset is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_library_asset 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 validate_library_asset. 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.
validate_library_asset 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