Search biochemical reactions by keywords or reaction components.
AI agents call search_reactions 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 search operation on the KEGG database to retrieve information about biochemical reactions. It has no side effects—it only reads and returns data based on search criteria. There is no modification of data, execution of code or commands, deletion of records, or financial transactions involved. This is a straightforward informational query tool.
From the tool's definition Tool description states it 'Search[es] biochemical reactions by keywords or reaction components.' The verb 'search' indicates a query operation that retrieves data without modification, creation, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access search_reactions 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_reactions:
{
"version": "1",
"default": "deny",
"tools": {
"search_reactions": {}
}
}search_reactions 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 biochemical reactions by keywords or reaction components. 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_reactions: 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_reactions 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_reactions 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_reactions. 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_reactions 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.