blender_scene_import
Create a self-contained TouchDesigner render scaffold for a Blender scene or Blender-exported asset: File In SOP (or fallback primitive), Geometry COMP, PBR material, environment/key lights, Camera, Render TOP, and Null TOP output. Supports .blend/.fbx/.obj/.gltf/.glb/.usd/.usdz paths and warns w...
This record as markdown: /tools/io-github-pantani-tdmcp/blender-scene-import.md
What blender_scene_import does on tdmcp — TouchDesigner MCP server
AI agents use blender_scene_import 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 blender_scene_import is rated Medium
This tool creates and adds new elements to a TouchDesigner project in a reversible manner. It does not execute arbitrary code, delete data, or commit financial transactions. While it modifies the project state by importing and scaffolding a render pipeline, these changes can be undone (typical file operations).
From the tool's definition Tool description states it creates 'a self-contained TouchDesigner render scaffold' with multiple components (File In SOP, Geometry COMP, PBR material, lights, Camera, Render TOP, Null TOP output).
Attacks that exploit this kind of access
The rule that runs blender_scene_import 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 blender_scene_import, this is the rule to start with:
blender_scene_import 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 blender_scene_import call is checked against it from then on.
Questions about blender_scene_import
Create a self-contained TouchDesigner render scaffold for a Blender scene or Blender-exported asset: File In SOP (or fallback primitive), Geometry COMP, PBR material, environment/key lights, Camera, Render TOP, and Null TOP output. Supports .blend/.fbx/.obj/.gltf/.glb/.usd/.usdz paths and warns when a .blend may need export from Blender first. 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 blender_scene_import: 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.
blender_scene_import 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 blender_scene_import 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 blender_scene_import. 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.
blender_scene_import 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