genesis_search_tools
Search all 1548 Genesis MCP operations across 32 services (agents, auto, beacons, blinds, boxes, brews, connections, dials, flares, fleets, flocks, foundry, garden, gateway, gears, henry, hives, iam, lanes, minds, one, orgs, panes, relays, rigs, runner, scopes, shells, silos, taps, traces, zaps) ...
This record as markdown: /tools/onesi-genesis-mcp/genesis-search-tools.md
What genesis_search_tools does on Genesis
AI agents call genesis_search_tools to retrieve information from Genesis 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 |
|---|---|---|---|
limit | integer | — | |
query | string | Yes | keywords, e.g. "dns record" or "deploy" |
service | string | — | optional service filter: agents | auto | beacons | blinds | boxes | brews | connections | dials | flares | fleets | flocks | foundry | garden | gateway | gears |
Parameters from the server's own tool schema.
Why genesis_search_tools is rated Low
Even though genesis_search_tools only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs genesis_search_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For genesis_search_tools, this is the rule to start with:
genesis_search_tools 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 Genesis, apply this rule, and every genesis_search_tools call is checked against it from then on.
Questions about genesis_search_tools
Search all 1548 Genesis MCP operations across 32 services (agents, auto, beacons, blinds, boxes, brews, connections, dials, flares, fleets, flocks, foundry, garden, gateway, gears, henry, hives, iam, lanes, minds, one, orgs, panes, relays, rigs, runner, scopes, shells, silos, taps, traces, zaps) by keyword. Returns operation ids and input schemas to use with genesis_call. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
genesis_search_tools accepts 3 parameters: limit, query, service. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for genesis_search_tools: 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 Genesis. Nothing to install.
genesis_search_tools 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 genesis_search_tools 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 genesis_search_tools. 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.
genesis_search_tools is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue