get_repairs
List active Home Assistant repair issues.
This record as markdown: /tools/fistacho-ha-nexus-agent/get-repairs.md
What get_repairs does on Ha Nexus Agent
AI agents call get_repairs 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 get_repairs is rated Low
This tool queries Home Assistant's repair system to retrieve information about active issues. It performs no data modification, deletion, or external actions—only information retrieval. The minimal blast radius and lack of consequential side effects classify it as Read with low severity.
From the tool's definition Tool name 'get_repairs' and description 'List active Home Assistant repair issues' indicate a read-only operation that retrieves and displays existing repair data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_repairs 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 get_repairs, this is the rule to start with:
get_repairs 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 get_repairs call is checked against it from then on.
Questions about get_repairs
List active Home Assistant repair issues. 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 get_repairs: 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.
get_repairs 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_repairs 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_repairs. 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_repairs 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