refresh_asset_previews
Capture fresh preview PNG assets from one or more live TOP nodes and write each target to its file_path. Use it to regenerate stale thumbnails after a network changes; pass targets as {node_path,file_path} plus optional width/height. Requires a running TouchDesigner bridge, overwrites image files...
This record as markdown: /tools/io-github-pantani-tdmcp/refresh-asset-previews.md
What refresh_asset_previews does on tdmcp — TouchDesigner MCP server
AI agents use refresh_asset_previews 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 refresh_asset_previews is rated Medium
The tool creates or modifies image files (PNG assets) by capturing previews and writing them to disk. While it overwrites existing files, this is a reversible write operation rather than irreversible deletion. The tool does not delete data permanently, execute arbitrary code, trigger financial transactions, or perform shell commands. It operates within a defined scope of regenerating preview thumbnails.
From the tool's definition Tool description explicitly states it will 'write each target to its file_path' and 'overwrites image files'. These are reversible file modifications.
Attacks that exploit this kind of access
The rule that runs refresh_asset_previews 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 refresh_asset_previews, this is the rule to start with:
refresh_asset_previews 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 refresh_asset_previews call is checked against it from then on.
Questions about refresh_asset_previews
Capture fresh preview PNG assets from one or more live TOP nodes and write each target to its file_path. Use it to regenerate stale thumbnails after a network changes; pass targets as {node_path,file_path} plus optional width/height. Requires a running TouchDesigner bridge, overwrites image files, and returns written previews plus per-target warnings. 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 refresh_asset_previews: 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.
refresh_asset_previews 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 refresh_asset_previews 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 refresh_asset_previews. 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.
refresh_asset_previews 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