mychem.chemicals.metadata
Retrieve build metadata and data source statistics for the MyChem.info API. Returns the current database build version (e.g. "20260525"), build date, total number of chemical records (197M+), and a list of integrated annotation sources with their versions, URLs, and license information. Sources i...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mychem.chemicals.metadata.md
What mychem.chemicals.metadata does on Apibase
AI agents call mychem.chemicals.metadata 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 |
|---|---|---|---|
detail | boolean | — | If true, include full source metadata with download dates, record counts per source, code repository links, and license URLs. If false (default), return only bu |
Parameters from the server's own tool schema.
Why mychem.chemicals.metadata is rated Low
Only retrieves metadata about the API; no side effects or data modification.
From the tool's definition Retrieve build metadata and data source statistics
Attacks that exploit this kind of access
The rule that runs mychem.chemicals.metadata 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.metadata, this is the rule to start with:
mychem.chemicals.metadata 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.metadata call is checked against it from then on.
Questions about mychem.chemicals.metadata
Retrieve build metadata and data source statistics for the MyChem.info API. Returns the current database build version (e.g. "20260525"), build date, total number of chemical records (197M+), and a list of integrated annotation sources with their versions, URLs, and license information. Sources include DrugBank, ChEMBL, ChEBI, PubChem, PharmGKB, SIDER, DrugCentral, UMLS, NDC, UniChem, GSRS, FDA Orphan Drug, GtoPdb (pharmacology), AEOLUS (adverse events), GINAS, and UNII. Use to verify data currency before large annotation jobs or to cite specific source versions in research publications. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
mychem.chemicals.metadata accepts 1 parameter: detail. 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.metadata: 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.metadata 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.metadata 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.metadata. 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.metadata 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