Search MyChem.info for drugs / chemical compounds. Accepts a plain drug name ("aspirin"), an InChIKey, or a fielded query (e.g. "chembl.pref_name:aspirin", "drugbank.name:Acetylsalicylic acid"). Returns aggregated hits with cross-references to ChEMBL, DrugBank, PubChem, ChEBI, DrugCentral, etc. U...
AI agents call query to retrieve information from Mcp Mychem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
size | number | — | Max hits to return, 1-1000 (default 10). |
query | string | Yes | Drug name ("aspirin"), an InChIKey, or a fielded query like "chembl.pref_name:aspirin". |
fields | string | — | Comma-separated return fields (default: all). e.g. "chembl.pref_name,drugbank.name,pubchem". |
Parameters from the server's own tool schema.
This tool retrieves and queries existing chemical database records. It performs no write, delete, execute, or financial operations. The blast radius of misuse is minimal — an AI agent could only retrieve irrelevant or excessive data, not modify systems or cause harm. This is a straightforward Read classification.
From the tool's definition Tool description states it 'Search[es] MyChem.info' and 'Returns aggregated hits' — purely retrieval operations with no modification, deletion, or execution capability.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search MyChem.info for drugs / chemical compounds. Accepts a plain drug name ("aspirin"), an InChIKey, or a fielded query (e.g. "chembl.pref_name:aspirin", "drugbank.name:Acetylsalicylic acid"). Returns aggregated hits with cross-references to ChEMBL, DrugBank, PubChem, ChEBI, DrugCentral, etc. Use this to resolve a drug name into structured identifiers. It is categorised as a Read tool in the Mcp Mychem MCP Server, which means it retrieves data without modifying state.
query accepts 3 parameters: size, query, fields. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Mychem MCP server in PolicyLayer and add a rule for query: 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 Mcp Mychem. Nothing to install.
query 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 query 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 query. 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.
query is provided by the Mcp Mychem MCP server (pipeworx-io/mcp-mychem). 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 →