setup_segmentation

One-shot selfie segmentation via the MediaPipe TouchDesigner engine (install with

High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/setup-segmentation.md

What setup_segmentation does on tdmcp — TouchDesigner MCP server

AI agents invoke setup_segmentation to trigger actions in tdmcp — TouchDesigner MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why setup_segmentation is rated High

This tool executes a segmentation pipeline using the MediaPipe engine within TouchDesigner, which involves running external processing operations. It is not a simple read/query, nor does it delete data or move money. The description is truncated, lowering confidence slightly, but the 'one-shot' execution pattern and engine invocation indicate Execute category.

From the tool's definition 'One-shot selfie segmentation via the MediaPipe TouchDesigner engine (install with...' — triggers an external engine/pipeline operation in TouchDesigner

Questions about setup_segmentation

What does the setup_segmentation tool do? +

One-shot selfie segmentation via the MediaPipe TouchDesigner engine (install with. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on setup_segmentation? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for setup_segmentation: 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.

What risk level is setup_segmentation? +

setup_segmentation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit setup_segmentation? +

Yes. Add a rate_limit block to the setup_segmentation 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.

How do I block setup_segmentation completely? +

Set action: deny in the PolicyLayer policy for setup_segmentation. 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.

What MCP server provides setup_segmentation? +

setup_segmentation 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.