search_ko_entries

THE RISK

Low Risk

Why search_ko_entries needs a policy

This tool performs a query operation against the KEGG database to find orthology entries matching specified criteria. No data is created, modified, deleted, or used to trigger external actions. It is a straightforward informational lookup with no blast radius if misused by an AI agent - the worst outcome would be retrieving irrelevant or excessive results, which is harmless.

From the tool's definition Tool description states 'Search KEGG Orthology entries' - a search operation that retrieves data with no modification or side effects. The verb 'search' combined with the read-only nature of querying a biological database indicates data retrieval only.

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

POLICY

How to control search_ko_entries

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_ko_entries:

policy.json

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

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Oh My KEGG MCP tools

Read batch_entry_lookup Process multiple KEGG entries efficiently. Read find_related_entries find_related_entries Read get_brite_info Get detailed information for a specific BRITE entry. Read get_compound_info Get detailed information for a specific compound. Read get_compound_reactions Get all reactions involving a specific compound. Read get_database_info get_database_info Read get_disease_info Get detailed information for a specific disease. Read get_drug_info Get detailed information for a specific drug.

All 33 Oh My KEGG MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_ko_entries

What does the search_ko_entries tool do? +

Search KEGG Orthology entries by function or gene name. 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_ko_entries? +

Register the Oh My KEGG MCP server in PolicyLayer and add a rule for search_ko_entries: 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_ko_entries? +

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

Can I rate-limit search_ko_entries? +

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

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

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

CHECK YOUR STACK →