import_model
Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP: a File In SOP reading
This record as markdown: /tools/io-github-pantani-tdmcp/import-model.md
What import_model does on tdmcp — TouchDesigner MCP server
AI agents use import_model 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 import_model is rated Medium
This tool creates and adds new data structures (model import + SOP operator) to a TouchDesigner project, which is reversible and matches the Write category. While it involves external file I/O, the primary action is creating/adding project components rather than destructively modifying or executing arbitrary code.
From the tool's definition Tool description states 'Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP', indicating it creates or modifies visual assets and project state within TouchDesigner by adding a new 3D model asset and associated operator (File In SOP) to the…
Attacks that exploit this kind of access
The rule that runs import_model 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 import_model, this is the rule to start with:
import_model 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 import_model call is checked against it from then on.
Questions about import_model
Import a 3D model file (.obj/.fbx/.usd) and render it to a TOP: a File In SOP reading. 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 import_model: 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.
import_model 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 import_model 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 import_model. 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.
import_model 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