get_hacs_repository
Get details about a single HACS repository by id.
This record as markdown: /tools/fistacho-ha-nexus-agent/get-hacs-repository.md
What get_hacs_repository does on Ha Nexus Agent
AI agents call get_hacs_repository 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_hacs_repository is rated Low
This tool retrieves information about a HACS (Home Assistant Community Store) repository. The verb 'get' and the lack of any modification language ('update', 'delete', 'create') clearly indicate a read-only operation. No data is created, modified, deleted, or financial operations are performed. The blast radius is minimal — it only returns existing repository metadata that would typically be publicly available.
From the tool's definition Tool name 'get_hacs_repository' and description 'Get details about a single HACS repository by id' indicate a retrieval operation that queries repository metadata without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_hacs_repository 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_hacs_repository, this is the rule to start with:
get_hacs_repository 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_hacs_repository call is checked against it from then on.
Questions about get_hacs_repository
Get details about a single HACS repository by id. 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_hacs_repository: 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_hacs_repository 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_hacs_repository 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_hacs_repository. 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_hacs_repository 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