auto_tag_library_asset
Inspect a captured library asset (a vault recipe/component note, or a live TD COMP) and emit a suggested tag set, difficulty, and one-line description from a deterministic operator-family heuristic; with write:true, merge the suggestion into the note
This record as markdown: /tools/io-github-pantani-tdmcp/auto-tag-library-asset.md
What auto_tag_library_asset does on tdmcp — TouchDesigner MCP server
AI agents use auto_tag_library_asset 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 auto_tag_library_asset is rated Medium
This tool primarily creates or modifies metadata (tags, difficulty ratings, descriptions) on library assets when write mode is enabled. While it performs inspection (Read), the key capability is reversible modification of asset metadata via the write:true flag. This qualifies as Write rather than Read due to the mutation capability.
From the tool's definition Tool performs 'merge the suggestion into the note' with 'write:true' parameter, modifying metadata. The description explicitly states it can write tags, difficulty, and descriptions to library asset notes.
Attacks that exploit this kind of access
The rule that runs auto_tag_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 auto_tag_library_asset, this is the rule to start with:
auto_tag_library_asset 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 auto_tag_library_asset call is checked against it from then on.
Questions about auto_tag_library_asset
Inspect a captured library asset (a vault recipe/component note, or a live TD COMP) and emit a suggested tag set, difficulty, and one-line description from a deterministic operator-family heuristic; with write:true, merge the suggestion into the note. 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 auto_tag_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.
auto_tag_library_asset 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 auto_tag_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 auto_tag_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.
auto_tag_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