setup_mediapipe_plugin
Drop the torinmb mediapipe-touchdesigner ENGINE in one shot and enable any combination of face, hand, body, and segmentation pipelines.
This record as markdown: /tools/hybridlabor-api-aos/setup-mediapipe-plugin.md
What setup_mediapipe_plugin does on Aos
AI agents use setup_mediapipe_plugin to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why setup_mediapipe_plugin is rated Medium
This tool sets up a MediaPipe plugin within TouchDesigner, which is a reversible creation/modification of the project configuration. It does not delete data, execute arbitrary code, move money, or trigger external side effects beyond configuring a vision-processing pipeline. The action is equivalent to adding a component or installing a library into the project (Write category).
From the tool's definition The tool "Drop the torinmb mediapipe-touchdesigner ENGINE in one shot and enable any combination of face, hand, body, and segmentation pipelines" creates and installs a plugin/engine into a TouchDesigner project.
Attacks that exploit this kind of access
The rule that runs setup_mediapipe_plugin 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_mediapipe_plugin, this is the rule to start with:
setup_mediapipe_plugin 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 Aos, apply this rule, and every setup_mediapipe_plugin call is checked against it from then on.
Questions about setup_mediapipe_plugin
Drop the torinmb mediapipe-touchdesigner ENGINE in one shot and enable any combination of face, hand, body, and segmentation pipelines. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for setup_mediapipe_plugin: 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_mediapipe_plugin 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 setup_mediapipe_plugin 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_mediapipe_plugin. 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_mediapipe_plugin 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