tool_search

A read tool on the Ha Nexus Agent MCP server.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/tool-search.md

WHAT IT DOES

What tool_search does on Ha Nexus Agent

AI agents call tool_search 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.

RISK

Why tool_search is rated Low

The tool name 'search' strongly suggests data retrieval without side effects. Given the Home Assistant context and the absence of a description indicating write or execute capability, this is classified as Read. Confidence is moderate (0.75) due to the empty description preventing full verification of actual behavior.

From the tool's definition Tool name 'search' combined with the Read category pattern (search, list, get, fetch) and empty description. No indication of modification or destructive capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tool_search 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 tool_search, this is the rule to start with:

tool_search Allowed

tool_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tool_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every tool_search call is checked against it from then on.

FAQ

Questions about tool_search

What does the tool_search tool do? +

tool_search is a read tool on the Ha Nexus Agent MCP server. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tool_search? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for tool_search: 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.

What risk level is tool_search? +

tool_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tool_search? +

Yes. Add a rate_limit block to the tool_search 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.

How do I block tool_search completely? +

Set action: deny in the PolicyLayer policy for tool_search. 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.

What MCP server provides tool_search? +

tool_search 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.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →