inspect_gpu_and_displays
Read-only: returns the host GPU info (name, driver, VRAM), attached monitor topology (resolution, refresh rate, primary flag, position), and whether the project is in Perform Mode. Use to plan output mapping, dome rigs, and multi-display shows without leaving the chat. Offline-safe — returns { co...
This record as markdown: /tools/io-github-pantani-tdmcp/inspect-gpu-and-displays.md
What inspect_gpu_and_displays does on tdmcp — TouchDesigner MCP server
AI agents call inspect_gpu_and_displays 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 inspect_gpu_and_displays is rated Low
This tool purely retrieves and queries system information (GPU details, monitor configuration, Perform Mode status) with no side effects. It is explicitly labeled 'Read-only' and produces informational output for planning purposes. The offline-safe fallback confirms it only gathers data.
From the tool's definition Tool name includes 'inspect' and description states 'Read-only: returns the host GPU info...attached monitor topology...whether the project is in Perform Mode.' No modification, deletion, or code execution described.
Attacks that exploit this kind of access
The rule that runs inspect_gpu_and_displays 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 inspect_gpu_and_displays, this is the rule to start with:
inspect_gpu_and_displays 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 inspect_gpu_and_displays call is checked against it from then on.
Questions about inspect_gpu_and_displays
Read-only: returns the host GPU info (name, driver, VRAM), attached monitor topology (resolution, refresh rate, primary flag, position), and whether the project is in Perform Mode. Use to plan output mapping, dome rigs, and multi-display shows without leaving the chat. Offline-safe — returns { connected: false, reason } when TD is unreachable. 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 inspect_gpu_and_displays: 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.
inspect_gpu_and_displays 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 inspect_gpu_and_displays 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 inspect_gpu_and_displays. 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.
inspect_gpu_and_displays 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