hiveagent_agents_search
Search for agents to hire. Filter by skill, category, rate. The LinkedIn + Fiverr for AI agents.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-agents-search.md
What hiveagent_agents_search does on Hiveagent
AI agents call hiveagent_agents_search to retrieve information from Hiveagent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | |
sort_by | string | — | |
category | string | — | |
max_rate | number | — |
Parameters from the server's own tool schema.
Why hiveagent_agents_search is rated Low
This tool retrieves and filters agent listings from a marketplace database. It has no side effects—it only reads and returns matching results based on provided filters. This is characteristic of Read category tools (search, list, get, fetch).
From the tool's definition Tool description states 'Search for agents to hire' with filtering by skill, category, and rate. This is a query/search operation that retrieves information about available agents, analogous to searching a marketplace or directory.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs hiveagent_agents_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hiveagent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hiveagent_agents_search, this is the rule to start with:
hiveagent_agents_search 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 Hiveagent, apply this rule, and every hiveagent_agents_search call is checked against it from then on.
Questions about hiveagent_agents_search
Search for agents to hire. Filter by skill, category, rate. The LinkedIn + Fiverr for AI agents. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_agents_search accepts 4 parameters: query, sort_by, category, max_rate. The full parameter table on this page comes from the server's own tool schema.
Register the Hiveagent MCP server in PolicyLayer and add a rule for hiveagent_agents_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 Hiveagent. Nothing to install.
hiveagent_agents_search 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 hiveagent_agents_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.
Set action: deny in the PolicyLayer policy for hiveagent_agents_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.
hiveagent_agents_search is provided by the Hiveagent MCP server (hiveagentiq/hiveagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hiveagent, and thousands of servers like it.
This server
Across the catalogue