get_technique_detail
Read-only: inspect embedded TouchDesigner technique packs and individual techniques, with optional code snippets and setup/workflow details.
This record as markdown: /tools/io-github-pantani-tdmcp/get-technique-detail.md
What get_technique_detail does on tdmcp — TouchDesigner MCP server
AI agents call get_technique_detail 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_technique_detail is rated Low
This tool only retrieves and queries information about existing technique packs and techniques in TouchDesigner. It does not create, modify, delete, or execute operations. The explicit 'Read-only' designation and the inspection/retrieval nature of the functionality place it firmly in the Read category with low severity, as misuse would only expose information without enabling destructive or consequential actions.
From the tool's definition Tool description explicitly states 'Read-only: inspect embedded TouchDesigner technique packs and individual techniques'. The verbs 'inspect' and 'read' confirm data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_technique_detail 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_technique_detail, this is the rule to start with:
get_technique_detail 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_technique_detail call is checked against it from then on.
Questions about get_technique_detail
Read-only: inspect embedded TouchDesigner technique packs and individual techniques, with optional code snippets and setup/workflow details. 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_technique_detail: 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_technique_detail 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_technique_detail 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_technique_detail. 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_technique_detail 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