Search for compounds by InChI or InChI key
AI agents call search_by_inchi 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 queries the PubChem chemical database to retrieve compound information based on chemical identifiers (InChI strings). It performs a lookup operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could enumerate compounds but cannot alter the database or trigger external operations. This is a straightforward Read operation.
From the tool's definition Tool description explicitly states 'Search for compounds' with query parameters (InChI/InChI key). The verb 'search' and lack of any modification language indicate data retrieval only.
Attacks that exploit this kind of access
Search for compounds by InChI or InChI key. 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_by_inchi: 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_by_inchi 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_by_inchi 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_by_inchi. 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_by_inchi is provided by the PubChem MCP Server MCP server (k-lordbodin7/pubchem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →