AI agents call search_enzymes 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 performs a read-only query operation against the KEGG database to retrieve enzyme information. No side effects, data modification, code execution, or deletions occur. The search function is a classic retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool is described as 'Search enzymes by EC number or enzyme name' - a search operation that retrieves enzyme data from the KEGG database without modifying or executing code.
Documented attack patterns abuse exactly the kind of access search_enzymes 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 search_enzymes:
{
"version": "1",
"default": "deny",
"tools": {
"search_enzymes": {}
}
}search_enzymes 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.
Search enzymes by EC number or enzyme name. 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 search_enzymes: 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.
search_enzymes 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 search_enzymes 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 search_enzymes. 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.
search_enzymes 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.