AI agents call search_kegg_pathway to retrieve information from Gwas 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 search operation against KEGG (Kyoto Encyclopedia of Genes and Genomes), a public reference database. It retrieves pathway information based on user-supplied search parameters (name or gene) but does not create, modify, delete, or execute code. The blast radius of misuse is minimal—incorrect queries simply return irrelevant results. Classification as Read is appropriate.
From the tool's definition Tool name 'search_kegg_pathway' and description 'Search KEGG for metabolic and signaling pathways by name or gene' indicate a query/retrieval operation against a public biological database with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search KEGG for metabolic and signaling pathways by name or gene. It is categorised as a Read tool in the Gwas MCP Server, which means it retrieves data without modifying state.
Register the Gwas MCP server in PolicyLayer and add a rule for search_kegg_pathway: 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 Gwas. Nothing to install.
search_kegg_pathway 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_kegg_pathway 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_kegg_pathway. 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_kegg_pathway is provided by the Gwas MCP server (muslus/gwas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →