scaffold_recipe_template
Write a minimal but valid recipe JSON template to disk as a starting point for a new recipe. Use it to bootstrap a hand-authored recipe that already passes RecipeSchema; fill in nodes/connections, then instantiate with apply_recipe. Writes a file (destructive).
This record as markdown: /tools/hybridlabor-api-aos/scaffold-recipe-template.md
What scaffold_recipe_template does on Aos
AI agents use scaffold_recipe_template to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why scaffold_recipe_template is rated Medium
This tool writes a JSON template file to disk, creating new data. While file writes can overwrite existing files, the primary intent is to create a recipe template as a starting point, not to irreversibly delete data. File overwrites are reversible (e.g., version control, backups) and typical Write operations.
From the tool's definition Description states: 'Write a minimal but valid recipe JSON template to disk as a starting point for a new recipe' and 'Writes a file (destructive)'.
Attacks that exploit this kind of access
The rule that runs scaffold_recipe_template 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 scaffold_recipe_template, this is the rule to start with:
scaffold_recipe_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 scaffold_recipe_template call is checked against it from then on.
Questions about scaffold_recipe_template
Write a minimal but valid recipe JSON template to disk as a starting point for a new recipe. Use it to bootstrap a hand-authored recipe that already passes RecipeSchema; fill in nodes/connections, then instantiate with apply_recipe. Writes a file (destructive). It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for scaffold_recipe_template: 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.
scaffold_recipe_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scaffold_recipe_template 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 scaffold_recipe_template. 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.
scaffold_recipe_template 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