search_operators
Search the embedded operator knowledge base (629 operators) by keyword, exact name, tag/keyword, category, subcategory, parameter metadata, or TouchDesigner version compatibility — ranked by relevance, fully offline by default. Use it to discover the right operator before creating nodes instead o...
This record as markdown: /tools/io-github-pantani-tdmcp/search-operators.md
What search_operators does on tdmcp — TouchDesigner MCP server
AI agents call search_operators 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_operators is rated Low
This tool retrieves and ranks information from a local knowledge base to help users find TouchDesigner operators by various criteria. It is a read-only search utility that does not modify state, execute code, or trigger external operations. The worst-case misuse would be discovering operators the user shouldn't know about, which poses minimal risk.
From the tool's definition Tool description states 'Search the embedded operator knowledge base' and 'discover the right operator' — purely a query/search operation with no side effects. No creation, modification, deletion, or code execution mentioned.
Attacks that exploit this kind of access
The rule that runs search_operators 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_operators, this is the rule to start with:
search_operators 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_operators call is checked against it from then on.
Questions about search_operators
Search the embedded operator knowledge base (629 operators) by keyword, exact name, tag/keyword, category, subcategory, parameter metadata, or TouchDesigner version compatibility — ranked by relevance, fully offline by default. Use it to discover the right operator before creating nodes instead of guessing a type (e.g. 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_operators: 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_operators 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_operators 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_operators. 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_operators 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