create_interactive_projection_mapping
Build a synthetic-safe interactive projection mapping rig for a USB webcam plus projector: camera/synthetic/existing TOP input, frame-difference motion field, placeholder blob/post-it mask, cyan dot and magenta card visual TOPs, manual Corner Pin projection mapping, debug switch, live controls, a...
This record as markdown: /tools/hybridlabor-api-aos/create-interactive-projection-mapping.md
What create_interactive_projection_mapping does on Aos
AI agents invoke create_interactive_projection_mapping 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 create_interactive_projection_mapping is rated High
This tool executes a multi-step construction operation in TouchDesigner, creating and connecting numerous operators/nodes into a live projection mapping rig. It doesn't merely store data (Write) — it triggers real-time external operations in a running TouchDesigner instance, including activating webcam input and configuring projection mapping hardware outputs.
From the tool's definition 'Build a synthetic-safe interactive projection mapping rig' — constructs and wires together a complex network of nodes (camera input, frame-difference motion field, blob/post-it mask, visual TOPs, Corner Pin projection mapping, debug switch, live controls,…
Attacks that exploit this kind of access
The rule that runs create_interactive_projection_mapping 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 create_interactive_projection_mapping, this is the rule to start with:
create_interactive_projection_mapping 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 create_interactive_projection_mapping call is checked against it from then on.
Questions about create_interactive_projection_mapping
Build a synthetic-safe interactive projection mapping rig for a USB webcam plus projector: camera/synthetic/existing TOP input, frame-difference motion field, placeholder blob/post-it mask, cyan dot and magenta card visual TOPs, manual Corner Pin projection mapping, debug switch, live controls, and an out1 Null TOP. Defaults to source=. 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 create_interactive_projection_mapping: 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.
create_interactive_projection_mapping 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 create_interactive_projection_mapping 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_interactive_projection_mapping. 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_interactive_projection_mapping 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