This record as markdown: /tools/hybridlabor-api-aos/setup-segmentation.md
What setup_segmentation does on Aos
AI agents invoke setup_segmentation to trigger actions in Aos. 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
Attacks that exploit this kind of access
The rule that runs setup_segmentation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setup_segmentation, this is the rule to start with:
setup_segmentation stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every setup_segmentation call is checked against it from then on.
Questions about setup_segmentation
One-shot selfie segmentation via the MediaPipe TouchDesigner engine (install with. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos 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 Aos. Nothing to install.
setup_segmentation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
setup_segmentation is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue