This record as markdown: /tools/gentel-lab-origenemcp/kegg-find.md
What kegg_find does on OrigeneMCP
AI agents call kegg_find to retrieve information from OrigeneMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why kegg_find is rated Low
The 'find' operation in the context of biomedical databases typically searches and retrieves reference information without modification. No destructive, executable, or financial operations are evident. Confidence is moderate (0.7) rather than high (0.9+) because the description is empty, requiring inference from name and context; however, the pattern is consistent with read-only query tools across the server.
From the tool's definition Tool name 'kegg_find' follows query/search naming patterns consistent with read-only database lookups. KEGG (Kyoto Encyclopedia of Genes and Genomes) is a biomedical reference database.
Attacks that exploit this kind of access
The rule that runs kegg_find safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OrigeneMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kegg_find, this is the rule to start with:
kegg_find is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OrigeneMCP, apply this rule, and every kegg_find call is checked against it from then on.
Questions about kegg_find
kegg_find is a read tool on the Origene MCP server. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.
Register the Origene MCP server in PolicyLayer and add a rule for kegg_find: 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 OrigeneMCP. Nothing to install.
kegg_find 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 kegg_find 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 kegg_find. 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.
kegg_find is provided by the Origene MCP server (gentel-lab/origenemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Origene, and thousands of servers like it.
This server
Across the catalogue