AI agents call get_ko_info 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.
This tool retrieves and queries existing biological data from the KEGG database without creating, modifying, or deleting any entries. It is a straightforward data lookup operation similar to sibling tools like 'get_compound_info' and 'get_disease_info', which are all informational retrieval functions.
From the tool's definition Tool name 'get_ko_info' and description 'Get detailed information for a specific KO entry' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access get_ko_info gives an agent:
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 get_ko_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_ko_info": {}
}
}get_ko_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information for a specific KO entry. It is categorised as a Read tool in the Oh My KEGG MCP MCP Server, which means it retrieves data without modifying state.
Register the Oh My KEGG MCP server in PolicyLayer and add a rule for get_ko_info: 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.
get_ko_info 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 get_ko_info 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 get_ko_info. 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.
get_ko_info 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.
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.