projector_calibration_wizard
Build a rehearsal-safe projector calibration network: generated grid/crosshair or selected source TOP, per-projector crop/corner-pin/level/output lanes, preview layout, notes, and brightness/gamma controls. Live projector alignment remains explicitly unverified until run on the physical outputs.
This record as markdown: /tools/io-github-pantani-tdmcp/projector-calibration-wizard.md
What projector_calibration_wizard does on tdmcp — TouchDesigner MCP server
AI agents invoke projector_calibration_wizard 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 projector_calibration_wizard is rated High
This tool executes configuration operations on external projector hardware systems. While framed as 'rehearsal-safe' (suggesting preview mode), it ultimately triggers projector control commands (alignment adjustments, brightness/gamma modifications, output lane configuration) that affect real physical devices.
From the tool's definition 'Build a rehearsal-safe projector calibration network','per-projector crop/corner-pin/level/output lanes','Live projector alignment','brightness/gamma controls' — the tool configures and controls physical projector outputs, generates calibration grids, and…
Attacks that exploit this kind of access
The rule that runs projector_calibration_wizard 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 projector_calibration_wizard, this is the rule to start with:
projector_calibration_wizard 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 tdmcp — TouchDesigner MCP server, apply this rule, and every projector_calibration_wizard call is checked against it from then on.
Questions about projector_calibration_wizard
Build a rehearsal-safe projector calibration network: generated grid/crosshair or selected source TOP, per-projector crop/corner-pin/level/output lanes, preview layout, notes, and brightness/gamma controls. Live projector alignment remains explicitly unverified until run on the physical outputs. 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.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for projector_calibration_wizard: 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.
projector_calibration_wizard 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 projector_calibration_wizard 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 projector_calibration_wizard. 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.
projector_calibration_wizard 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.
Across the catalogue