genesis_search_tools

Search all 348 Genesis API operations (Foundry, Hives, Relays, IAM...) by keyword. Returns operation ids and input schemas to use with genesis_call.

SERVERGenesis SOURCE@lifesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/genesis-search-tools.md

WHAT IT DOES

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: foundry \| hives \| relays \| iam

Parameters from the server's own tool schema.

RISK

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

RECOMMENDED RULE

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 Allowed

genesis_search_tools 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": {
    "genesis_search_tools": {}
  }
}

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

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.

FAQ

Questions about genesis_search_tools

What does the genesis_search_tools tool do? +

Search all 348 Genesis API operations (Foundry, Hives, Relays, IAM...) 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.

What parameters does genesis_search_tools accept? +

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.

How do I enforce a policy on genesis_search_tools? +

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.

What risk level is genesis_search_tools? +

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

Can I rate-limit genesis_search_tools? +

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.

How do I block genesis_search_tools completely? +

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.

What MCP server provides genesis_search_tools? +

genesis_search_tools is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 252 Genesis tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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