refresh_index
Force-rebuild the search index (run after dynamically adding tools at runtime).
This record as markdown: /tools/fistacho-ha-nexus-agent/refresh-index.md
What refresh_index does on Ha Nexus Agent
AI agents invoke refresh_index 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 refresh_index is rated High
This tool executes a rebuild operation on system infrastructure (the search index). While not destructive in the sense of permanent data loss, it performs a computational operation that modifies system state and could impact availability or performance of the smart home system during execution.
From the tool's definition Tool performs a force-rebuild operation on a search index; described as an action to 'run after dynamically adding tools at runtime', indicating it triggers an external operation with side effects rather than retrieving data.
Attacks that exploit this kind of access
The rule that runs refresh_index 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 refresh_index, this is the rule to start with:
refresh_index 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 refresh_index call is checked against it from then on.
Questions about refresh_index
Force-rebuild the search index (run after dynamically adding tools at runtime). 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 refresh_index: 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.
refresh_index 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 refresh_index 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 refresh_index. 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.
refresh_index 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