Low Risk

get_compound_info

Get detailed information for a specific compound.

How to control get_compound_info ↓

What get_compound_info does on Oh My KEGG MCP

AI agents call get_compound_info 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.

Low Risk

Why get_compound_info needs a policy

This tool retrieves and queries compound information from the KEGG database. The verb 'Get' and the absence of any language indicating creation, modification, deletion, or execution of code confirms this is a read-only operation. The biological/scientific nature of the data does not elevate the risk—misuse would amount to unauthorized access to public scientific data, which carries minimal real-world harm.

From the tool's definition Tool name 'get_compound_info' and description 'Get detailed information for a specific compound' indicate retrieval of data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_compound_info gives an agent:

How to control get_compound_info

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 get_compound_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_compound_info": {}
  }
}

get_compound_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Oh My KEGG MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_compound_info

What does the get_compound_info tool do? +

Get detailed information for a specific compound. It is categorised as a Read tool in the Oh My KEGG MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_compound_info? +

Register the Oh My KEGG MCP server in PolicyLayer and add a rule for get_compound_info: 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.

What risk level is get_compound_info? +

get_compound_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_compound_info? +

Yes. Add a rate_limit block to the get_compound_info 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.

How do I block get_compound_info completely? +

Set action: deny in the PolicyLayer policy for get_compound_info. 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.

What MCP server provides get_compound_info? +

get_compound_info 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.

Enforce policy on every Oh My KEGG MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.