AI agents call batch_entry_lookup 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 or queries multiple entries from the KEGG database without creating, modifying, or deleting data. It produces no side effects beyond data retrieval. The batch operation scales the read capability but does not change the fundamental nature of the operation. Severity is low because misuse would only result in excessive queries, not data corruption or unauthorized actions.
From the tool's definition Tool name 'batch_entry_lookup' and description 'Process multiple KEGG entries efficiently' indicate a query/retrieval operation with no modification or destructive capability.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_entry_lookup 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 batch_entry_lookup:
{
"version": "1",
"default": "deny",
"tools": {
"batch_entry_lookup": {}
}
}batch_entry_lookup 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.
Process multiple KEGG entries efficiently. 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 batch_entry_lookup: 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.
batch_entry_lookup 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 batch_entry_lookup 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 batch_entry_lookup. 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.
batch_entry_lookup 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.