build_from_recipe
A execute tool on the Ha Nexus Agent MCP server.
This record as markdown: /tools/fistacho-ha-nexus-agent/build-from-recipe.md
What build_from_recipe does on Ha Nexus Agent
AI agents invoke build_from_recipe to trigger actions in Ha Nexus Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why build_from_recipe is rated High
Given the broad Execute-category nature of Home Assistant and the sibling tools showing automation/scene activation (activate_scene, abort_config_flow), 'build_from_recipe' most likely constructs and executes a smart home recipe or routine, making it Execute rather than Write. However, the empty description prevents higher confidence.
From the tool's definition Tool name is 'build_from_recipe' in the Home Assistant smart home control server context. The empty description limits confidence, but 'build' suggests triggering or constructing something (likely automation, scene, or device configuration).
Attacks that exploit this kind of access
The rule that runs build_from_recipe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_from_recipe, this is the rule to start with:
build_from_recipe stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every build_from_recipe call is checked against it from then on.
Questions about build_from_recipe
build_from_recipe is a execute tool on the Ha Nexus Agent MCP server. It is categorised as a Execute tool in the Ha Nexus Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for build_from_recipe: 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 Ha Nexus Agent. Nothing to install.
build_from_recipe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_from_recipe 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 build_from_recipe. 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.
build_from_recipe is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue