get_td_class_details
AI agents call get_td_class_details to retrieve information from Touchdesigner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about TouchDesigner classes—a read-only operation with no side effects. Even if it exposes internal API details, it does not create, modify, delete, or execute arbitrary operations. The lack of description lowers confidence slightly, but the naming pattern and server purpose (introspection is explicitly mentioned) clearly indicate a data retrieval function.
From the tool's definition Tool name 'get_td_class_details' indicates retrieval of class information from the TouchDesigner API. The description is empty, but the name and context of sibling tools (which include introspection operations like 'find_operators') suggest this performs API…
Attacks that exploit this kind of access
get_td_class_details. It is categorised as a Read tool in the Touchdesigner MCP Server, which means it retrieves data without modifying state.
Register the Touchdesigner MCP server in PolicyLayer and add a rule for get_td_class_details: 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 Touchdesigner. Nothing to install.
get_td_class_details 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_td_class_details 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_td_class_details. 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_td_class_details is provided by the Touchdesigner MCP server (mrinalghosh/touchdesigner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →