create_sam2_segmentation_bridge
Build a TouchDesigner bridge surface for an external SAM2/FastSAM segmentation service.
This record as markdown: /tools/io-github-pantani-tdmcp/create-sam2-segmentation-bridge.md
What create_sam2_segmentation_bridge does on tdmcp — TouchDesigner MCP server
AI agents use create_sam2_segmentation_bridge 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 create_sam2_segmentation_bridge is rated Medium
This tool creates a new component/bridge surface within TouchDesigner, which is a write/create operation. It establishes a connection bridge to an external service but does not execute arbitrary code, delete data, or involve financial transactions. The blast radius is medium as it modifies the TouchDesigner project by adding new nodes/structures.
From the tool's definition 'Build a TouchDesigner bridge surface for an external SAM2/FastSAM segmentation service'
Attacks that exploit this kind of access
The rule that runs create_sam2_segmentation_bridge 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 create_sam2_segmentation_bridge, this is the rule to start with:
create_sam2_segmentation_bridge 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 create_sam2_segmentation_bridge call is checked against it from then on.
Questions about create_sam2_segmentation_bridge
Build a TouchDesigner bridge surface for an external SAM2/FastSAM segmentation service. 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 create_sam2_segmentation_bridge: 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.
create_sam2_segmentation_bridge 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 create_sam2_segmentation_bridge 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 create_sam2_segmentation_bridge. 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.
create_sam2_segmentation_bridge 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