search_touchdesigner_knowledge
Read-only: search the embedded TouchDesigner knowledge router across operators, operator workflows, examples, versions, compatibility notes, technique packs, TD classes, and experimental build notes. Returns normalized results with resource URIs and tool hints for deeper lookups.
This record as markdown: /tools/io-github-pantani-tdmcp/search-touchdesigner-knowledge.md
What search_touchdesigner_knowledge does on tdmcp — TouchDesigner MCP server
AI agents call search_touchdesigner_knowledge 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 search_touchdesigner_knowledge is rated Low
This is a pure information retrieval tool that searches a static knowledge base (operators, workflows, examples, etc.). It has no side effects, cannot modify state, and cannot trigger external operations. The 'read-only' designation and the nature of searching documentation/examples confirm it poses minimal security risk—appropriate for low severity.
From the tool's definition Description explicitly states 'Read-only: search the embedded TouchDesigner knowledge router' with 'Returns normalized results'. The tool queries a knowledge base without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs search_touchdesigner_knowledge 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 search_touchdesigner_knowledge, this is the rule to start with:
search_touchdesigner_knowledge 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 search_touchdesigner_knowledge call is checked against it from then on.
Questions about search_touchdesigner_knowledge
Read-only: search the embedded TouchDesigner knowledge router across operators, operator workflows, examples, versions, compatibility notes, technique packs, TD classes, and experimental build notes. Returns normalized results with resource URIs and tool hints for deeper lookups. 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 search_touchdesigner_knowledge: 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.
search_touchdesigner_knowledge 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 search_touchdesigner_knowledge 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 search_touchdesigner_knowledge. 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.
search_touchdesigner_knowledge 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