AI agents call search_brite 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.
Without a description, confidence is slightly reduced, but the tool name 'search_brite' and the pattern of sibling tools all being Read-category (get_*, find_*, search_) strongly suggest this is a data retrieval operation. BRITE searches do not modify data, execute code, or cause destructive changes. Classification as Read is appropriate.
From the tool's definition Tool name is 'search_brite' with empty description. BRITE is KEGG's hierarchical classification system. The 'search' verb and sibling tools (batch_entry_lookup, find_related_entries, get_*_info) indicate this retrieves/queries data without side effects.
Documented attack patterns abuse exactly the kind of access search_brite 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_brite:
{
"version": "1",
"default": "deny",
"tools": {
"search_brite": {}
}
}search_brite 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_brite. 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_brite: 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_brite 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_brite 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_brite. 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_brite 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.