recipe_guide
Embedded how-to for designing Card Builder cards programmatically.
This record as markdown: /tools/fistacho-ha-nexus-agent/recipe-guide.md
What recipe_guide does on Ha Nexus Agent
AI agents call recipe_guide to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why recipe_guide is rated Low
The tool serves as a reference guide or tutorial for learning how to design cards in Home Assistant's Card Builder. Reading embedded documentation has no side effects and does not alter the home automation system's configuration or state. This is a pure Read operation with minimal blast radius.
From the tool's definition Tool description states 'Embedded how-to for designing Card Builder cards programmatically' — this is documentation/guidance material that retrieves or presents instructional content without executing actions or modifying system state.
Attacks that exploit this kind of access
The rule that runs recipe_guide 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 recipe_guide, this is the rule to start with:
recipe_guide 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 Ha Nexus Agent, apply this rule, and every recipe_guide call is checked against it from then on.
Questions about recipe_guide
Embedded how-to for designing Card Builder cards programmatically. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for recipe_guide: 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.
recipe_guide 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 recipe_guide 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 recipe_guide. 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.
recipe_guide 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.
This server
Across the catalogue