AI agents call search_pubchem_by_name 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 searches a read-only public database (PubChem) and retrieves chemical compound data by name. No data is created, modified, deleted, or modified. It has no side effects beyond returning query results. Confidence is not higher due to the empty description, but the name and server context clearly indicate a retrieval/search function with no destructive or operational capabilities.
From the tool's definition Tool name 'search_pubchem_by_name' combined with server description stating it 'search[es] and retriev[es] chemical compound information' indicates a query operation.
Documented attack patterns abuse exactly the kind of access search_pubchem_by_name 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 search_pubchem_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"search_pubchem_by_name": {}
}
}search_pubchem_by_name 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.
search_pubchem_by_name. 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 search_pubchem_by_name: 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.
search_pubchem_by_name 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 search_pubchem_by_name 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 search_pubchem_by_name. 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.
search_pubchem_by_name 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.