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...

Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about search_operators

What does the search_operators tool do? +

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.

How do I enforce a policy on search_operators? +

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.

What risk level is search_operators? +

search_operators is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_operators? +

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.

How do I block search_operators completely? +

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.

What MCP server provides search_operators? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.