get_operator_workflow_guide
Read-only: return an embedded TouchDesigner operator workflow guide with common inputs, outputs, examples, and next-operator suggestions. For unknown operators, returns candidate guide ids instead of failing.
This record as markdown: /tools/io-github-pantani-tdmcp/get-operator-workflow-guide.md
What get_operator_workflow_guide does on tdmcp — TouchDesigner MCP server
AI agents call get_operator_workflow_guide 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 get_operator_workflow_guide is rated Low
This tool retrieves and queries static or semi-static reference documentation about TouchDesigner operators. It has no capability to modify project state, execute operations, or trigger external systems. The 'Read-only' declaration and pure information-return nature classify it as a Read operation with low severity risk.
From the tool's definition Tool description explicitly states 'Read-only' and describes returning an embedded workflow guide with no modification of data or triggering of external operations.
Attacks that exploit this kind of access
The rule that runs get_operator_workflow_guide 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 get_operator_workflow_guide, this is the rule to start with:
get_operator_workflow_guide 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 get_operator_workflow_guide call is checked against it from then on.
Questions about get_operator_workflow_guide
Read-only: return an embedded TouchDesigner operator workflow guide with common inputs, outputs, examples, and next-operator suggestions. For unknown operators, returns candidate guide ids instead of failing. 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 get_operator_workflow_guide: 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.
get_operator_workflow_guide 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 get_operator_workflow_guide 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 get_operator_workflow_guide. 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.
get_operator_workflow_guide 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