AI agents call get_pubchem_compound_by_cid to retrieve information from PubChem MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves molecular data from PubChem using a compound identifier (CID). It performs a GET/fetch operation on public chemical data with no capability to modify, delete, or execute code. The tool has minimal blast radius if misused—worst case is excessive queries or information disclosure of publicly available chemical data.
From the tool's definition Tool name 'get_pubchem_compound_by_cid' indicates retrieval of compound data by CID identifier. Server description confirms this is for 'retrieve chemical compound information, structures, and physical properties' with 'no side effects' implied by read-only…
Documented attack patterns abuse exactly the kind of access get_pubchem_compound_by_cid gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PubChem MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pubchem_compound_by_cid:
{
"version": "1",
"default": "deny",
"tools": {
"get_pubchem_compound_by_cid": {}
}
}get_pubchem_compound_by_cid is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_pubchem_compound_by_cid. It is categorised as a Read tool in the PubChem MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PubChem MCP Server MCP server in PolicyLayer and add a rule for get_pubchem_compound_by_cid: 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 PubChem MCP Server. Nothing to install.
get_pubchem_compound_by_cid 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 get_pubchem_compound_by_cid 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 get_pubchem_compound_by_cid. 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.
get_pubchem_compound_by_cid is provided by the PubChem MCP Server MCP server (jackkuo666/pubchem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PubChem MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 PubChem MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.