mychem.chemicals.batch_query
Retrieve annotations for up to 100 chemical compounds in a single request by providing an array of chemical names or identifiers. Returns ChEBI name, ChEMBL preferred name and clinical phase, PubChem CID, molecular formula and weight, DrugBank drug groups, and PharmGKB name for each compound in o...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mychem.chemicals.batch-query.md
What mychem.chemicals.batch_query does on Apibase
AI agents call mychem.chemicals.batch_query to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | array | Yes | Array of chemical queries to look up in a single request. Each element can be a chemical name, synonym, or identifier (up to 100 entries). Example: ["aspirin", |
fields | string | — | Comma-separated annotation fields to return for each chemical. Default: chebi.name, chebi.definition, chebi.formula, chebi.mass, chembl.pref_name, chembl.max_ph |
scopes | string | — | Comma-separated fields to search within for each query in the batch. Default: chebi.name,chembl.pref_name,drugbank.name,pubchem.cid — searches across common nam |
Parameters from the server's own tool schema.
Why mychem.chemicals.batch_query is rated Low
Tool retrieves and enriches chemical data without modifying, deleting, or executing operations.
From the tool's definition Retrieve annotations for up to 100 chemical compounds in a single request
Attacks that exploit this kind of access
The rule that runs mychem.chemicals.batch_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mychem.chemicals.batch_query, this is the rule to start with:
mychem.chemicals.batch_query 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 Apibase, apply this rule, and every mychem.chemicals.batch_query call is checked against it from then on.
Questions about mychem.chemicals.batch_query
Retrieve annotations for up to 100 chemical compounds in a single request by providing an array of chemical names or identifiers. Returns ChEBI name, ChEMBL preferred name and clinical phase, PubChem CID, molecular formula and weight, DrugBank drug groups, and PharmGKB name for each compound in one call. Ideal for enriching compound lists from drug screening assays, annotating molecule libraries, building pharmacology databases, or cross-referencing chemicals across naming conventions (INN, brand names, IUPAC names). Compounds not found in any database are marked with found=false. Mix different name formats and identifiers freely in a single batch request. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
mychem.chemicals.batch_query accepts 3 parameters: q, fields, scopes. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for mychem.chemicals.batch_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 Apibase. Nothing to install.
mychem.chemicals.batch_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 mychem.chemicals.batch_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 mychem.chemicals.batch_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.
mychem.chemicals.batch_query is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue