chembl.molecules.detail
Retrieve full structural and pharmacological data for a specific ChEMBL molecule. Returns canonical SMILES, standard InChI, InChIKey, molecular formula, exact weight, ALogP, polar surface area, hydrogen bond count, QED drug-likeness score (0–1), Lipinski rule-of-5 violations, black box warning fl...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/chembl.molecules.detail.md
What chembl.molecules.detail does on Apibase
AI agents call chembl.molecules.detail 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 |
|---|---|---|---|
chembl_id | string | Yes | ChEMBL molecule identifier (e.g. CHEMBL25 for aspirin, CHEMBL521 for ibuprofen). Use chembl.molecule.search to find IDs by name. |
Parameters from the server's own tool schema.
Why chembl.molecules.detail is rated Low
Tool retrieves public chemical/pharmacological data with no side effects, creation, modification, or deletion capabilities.
From the tool's definition Retrieve full structural and pharmacological data for specific ChEMBL molecule.
Attacks that exploit this kind of access
The rule that runs chembl.molecules.detail 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 chembl.molecules.detail, this is the rule to start with:
chembl.molecules.detail 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 chembl.molecules.detail call is checked against it from then on.
Questions about chembl.molecules.detail
Retrieve full structural and pharmacological data for a specific ChEMBL molecule. Returns canonical SMILES, standard InChI, InChIKey, molecular formula, exact weight, ALogP, polar surface area, hydrogen bond count, QED drug-likeness score (0–1), Lipinski rule-of-5 violations, black box warning flag, natural product flag, clinical phase (max_phase), first approval year, ATC codes, and administration routes. Use chembl.molecules.search to discover ChEMBL IDs (format: CHEMBL25, CHEMBL521). Source: EMBL-EBI ChEMBL — CC BY-SA 3.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
chembl.molecules.detail accepts 1 parameter: chembl_id. Required: chembl_id. 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 chembl.molecules.detail: 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.
chembl.molecules.detail 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 chembl.molecules.detail 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 chembl.molecules.detail. 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.
chembl.molecules.detail 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