Fetch the full aggregated annotation for a single chemical / drug by id. The id is typically an InChIKey (e.g. "BSYNRYMUTXBXSQ-UHFFFAOYSA-N"), but a DrugBank id, ChEMBL id, or other source id also works. Returns merged annotations from ChEMBL, DrugBank, PubChem, ChEBI, DrugCentral, etc., includin...
AI agents call chem 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 |
|---|---|---|---|
id | string | Yes | An InChIKey like "BSYNRYMUTXBXSQ-UHFFFAOYSA-N", or a DrugBank / ChEMBL id. |
fields | string | — | Comma-separated return fields (default: all). |
Parameters from the server's own tool schema.
The tool retrieves and queries chemical/drug metadata and annotations from multiple databases. It has no side effects, performs no modifications, executions, deletions, or financial operations. The action is purely informational retrieval, which is characteristic of the Read category.
From the tool's definition Fetch the full aggregated annotation for a single chemical / drug by id... Returns merged annotations from ChEMBL, DrugBank, PubChem, ChEBI, DrugCentral, etc.
Attacks that exploit this kind of access
Fetch the full aggregated annotation for a single chemical / drug by id. The id is typically an InChIKey (e.g. "BSYNRYMUTXBXSQ-UHFFFAOYSA-N"), but a DrugBank id, ChEMBL id, or other source id also works. Returns merged annotations from ChEMBL, DrugBank, PubChem, ChEBI, DrugCentral, etc., including mechanism, indication, and pharmacology cross-references. It is categorised as a Read tool in the Mcp Mychem MCP Server, which means it retrieves data without modifying state.
chem accepts 2 parameters: id, fields. Required: id. 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 chem: 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.
chem 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 chem 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 chem. 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.
chem 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 →