diagnose_hardware_environment
Read-only: check whether TouchDesigner is reachable, whether display/projector topology matches expectations, and whether generated sensor/helper status DATs such as source_status or bridge_status are healthy. This is a room/hardware preflight for physical installations; it returns PASS/WARNING/F...
This record as markdown: /tools/io-github-pantani-tdmcp/diagnose-hardware-environment.md
What diagnose_hardware_environment does on tdmcp — TouchDesigner MCP server
AI agents call diagnose_hardware_environment to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why diagnose_hardware_environment is rated Low
This tool performs diagnostic queries and status checks of the TouchDesigner environment and physical hardware topology. It retrieves and reports state information (hardware connectivity, display configuration, sensor status) without creating, modifying, deleting, or executing any operations that change system state.
From the tool's definition Tool description explicitly states 'Read-only' and 'returns PASS/WARNING/FAIL/UNVERIFIED checks without mutating the TD project.' The tool 'check[s] whether TouchDesigner is reachable' and validates hardware/sensor status—pure information retrieval with no…
Attacks that exploit this kind of access
The rule that runs diagnose_hardware_environment 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 diagnose_hardware_environment, this is the rule to start with:
diagnose_hardware_environment is read-only, so it stays allowed. 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 diagnose_hardware_environment call is checked against it from then on.
Questions about diagnose_hardware_environment
Read-only: check whether TouchDesigner is reachable, whether display/projector topology matches expectations, and whether generated sensor/helper status DATs such as source_status or bridge_status are healthy. This is a room/hardware preflight for physical installations; it returns PASS/WARNING/FAIL/UNVERIFIED checks without mutating the TD project. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for diagnose_hardware_environment: 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.
diagnose_hardware_environment is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the diagnose_hardware_environment 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 diagnose_hardware_environment. 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.
diagnose_hardware_environment 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.
This server
Across the catalogue