draft_recipe_from_technique
Read-only: convert an embedded TouchDesigner technique with GLSL source into a RecipeSchema draft without writing files or touching the TD bridge.
This record as markdown: /tools/hybridlabor-api-aos/draft-recipe-from-technique.md
What draft_recipe_from_technique does on Aos
AI agents call draft_recipe_from_technique 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 draft_recipe_from_technique is rated Low
This tool retrieves and transforms existing TouchDesigner technique data into a schema draft. It performs analysis and conversion operations without modifying state, creating files, executing code, or triggering external operations. The explicit 'Read-only' designation confirms it has no side effects. The operation is purely informational/analytical, making it a Read category tool with low severity.
From the tool's definition Tool description explicitly states 'Read-only' and clarifies it does not write files or touch the TD bridge. It converts/analyzes existing technique data into a schema representation without side effects.
Attacks that exploit this kind of access
The rule that runs draft_recipe_from_technique 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 draft_recipe_from_technique, this is the rule to start with:
draft_recipe_from_technique 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 draft_recipe_from_technique call is checked against it from then on.
Questions about draft_recipe_from_technique
Read-only: convert an embedded TouchDesigner technique with GLSL source into a RecipeSchema draft without writing files or touching the TD bridge. 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 draft_recipe_from_technique: 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.
draft_recipe_from_technique 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 draft_recipe_from_technique 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 draft_recipe_from_technique. 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.
draft_recipe_from_technique 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