Low Risk

search_diseases

Search human diseases by name or keywords.

How to control search_diseases ↓

What search_diseases does on Oh My KEGG MCP

AI agents call search_diseases to retrieve information from Oh My KEGG MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_diseases needs a policy

This tool retrieves information from the KEGG database about diseases based on search criteria. It performs a read-only query operation without creating, modifying, deleting, or executing any external operations. The search function is a standard information retrieval operation with no blast radius if misused by an AI agent.

From the tool's definition Tool description states it "Search[es] human diseases by name or keywords" - a query operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access search_diseases gives an agent:

How to control search_diseases

PolicyLayer is an MCP gateway — it sits between your AI agents and Oh My KEGG MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_diseases:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_diseases": {}
  }
}

search_diseases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Oh My KEGG MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_diseases

What does the search_diseases tool do? +

Search human diseases by name or keywords. It is categorised as a Read tool in the Oh My KEGG MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_diseases? +

Register the Oh My KEGG MCP server in PolicyLayer and add a rule for search_diseases: 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 Oh My KEGG MCP. Nothing to install.

What risk level is search_diseases? +

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

Can I rate-limit search_diseases? +

Yes. Add a rate_limit block to the search_diseases 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 search_diseases completely? +

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

search_diseases is provided by the Oh My KEGG MCP server (martinuslee/oh-my-kegg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Oh My KEGG MCP tool call.

Start from Oh My KEGG MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

33 Oh My KEGG MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.