get_td_performance
Read-only: report cook times under a network (recursively by default, slowest node first) and warn about nodes that exceed the frame budget. Returns {targetFps, frameBudgetMs, totalCookMs, nodes[], warnings[]} and changes nothing. Use this to just measure; use optimize_performance when you want s...
This record as markdown: /tools/hybridlabor-api-aos/get-td-performance.md
What get_td_performance does on Aos
AI agents call get_td_performance to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_td_performance is rated Low
This tool retrieves and queries performance data from a TouchDesigner network. It has no side effects—it only measures and reports cook times and warnings without creating, modifying, deleting, or executing any operations. The explicit 'Read-only' designation and 'changes nothing' confirmation place it firmly in the Read category with minimal risk.
From the tool's definition Tool description explicitly states 'Read-only: report cook times' and 'changes nothing'. It returns performance metrics without modifying any state or triggering external operations.
Attacks that exploit this kind of access
The rule that runs get_td_performance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_td_performance, this is the rule to start with:
get_td_performance 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 Aos, apply this rule, and every get_td_performance call is checked against it from then on.
Questions about get_td_performance
Read-only: report cook times under a network (recursively by default, slowest node first) and warn about nodes that exceed the frame budget. Returns {targetFps, frameBudgetMs, totalCookMs, nodes[], warnings[]} and changes nothing. Use this to just measure; use optimize_performance when you want suggestions and the option to auto-shrink the slow TOPs. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for get_td_performance: 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 Aos. Nothing to install.
get_td_performance 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_performance 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_performance. 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_performance is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue