check_operator_availability

What check_operator_availability does on tdmcp — TouchDesigner MCP server

AI agents call check_operator_availability 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 check_operator_availability is rated Low

The tool retrieves and validates operator availability by comparing a knowledge base against the current TouchDesigner runtime state. This is a read-only diagnostic operation with no side effects—it does not create, modify, delete, or execute code. The word 'reconcile' in this context means to compare/verify, not to alter. Blast radius is minimal since the tool cannot affect the project, parameters, or execution.

From the tool's definition Tool name 'check_operator_availability' and description 'Reconcile the operator knowledge base against the RUNNING TouchDesigner' indicate a query/verification operation that checks and compares data without modifying state.

The rule that runs check_operator_availability 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 check_operator_availability, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_operator_availability": {}
  }
}

Questions about check_operator_availability