science.chem.resolve
Convert any chemical identifier to SMILES, InChI, and InChIKey. Input a compound name (e.g. "aspirin"), CAS number (e.g. "50-78-2"), SMILES, or InChIKey and get all other representations. The only universal chemical ID converter — essential for chemistry workflows and cross-database lookups (NCI ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/science.chem.resolve.md
What science.chem.resolve does on Apibase
AI agents call science.chem.resolve 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 |
|---|---|---|---|
output | string | — | Output format: "all" (SMILES + InChI + InChIKey), "smiles" (canonical SMILES only), "stdinchi" (Standard InChI only), "stdinchikey" (InChIKey only). Default: "a |
identifier | string | Yes | Chemical identifier to resolve — compound name (e.g. "aspirin", "caffeine"), CAS number (e.g. "50-78-2"), SMILES (e.g. "CC(=O)Oc1ccccc1C(O)=O"), or InChIKey (e. |
Parameters from the server's own tool schema.
Why science.chem.resolve is rated Low
Tool retrieves and transforms chemical identifiers without modifying data or triggering side effects.
From the tool's definition Convert chemical identifier to SMILES, InChI, InChIKey; lookup only
Attacks that exploit this kind of access
The rule that runs science.chem.resolve 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 science.chem.resolve, this is the rule to start with:
science.chem.resolve 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 science.chem.resolve call is checked against it from then on.
Questions about science.chem.resolve
Convert any chemical identifier to SMILES, InChI, and InChIKey. Input a compound name (e.g. "aspirin"), CAS number (e.g. "50-78-2"), SMILES, or InChIKey and get all other representations. The only universal chemical ID converter — essential for chemistry workflows and cross-database lookups (NCI CACTUS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
science.chem.resolve accepts 2 parameters: output, identifier. Required: identifier. 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 science.chem.resolve: 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.
science.chem.resolve 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 science.chem.resolve 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 science.chem.resolve. 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.
science.chem.resolve 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