AI agents call get_chemical_info 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 is a pure read operation that queries a public chemical database to fetch existing data. There are no side effects, no state changes, no code execution, and no financial implications. The tool merely returns chemical property information, which is a standard data retrieval operation.
From the tool's definition Tool retrieves 'detailed information' about chemical substances from PubChem API. Server description confirms it 'retrieves' and 'enables users to retrieve molecular details such as SMILES, IUPAC names, molecular formulas, and synonyms' with no mention of…
Documented attack patterns abuse exactly the kind of access get_chemical_info 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_chemical_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_chemical_info": {}
}
}get_chemical_info 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.
获取化学物质的详细信息. 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_chemical_info: 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_chemical_info 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_chemical_info 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_chemical_info. 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_chemical_info is provided by the PubChem MCP Server MCP server (sssjiang/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.
3 PubChem MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.