Run RDKit substructure search over indexed RDF molfile structures.
AI agents call substructure_search_structures to retrieve information from Scifinder Route without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Substructure searching is a read-only query operation against an indexed chemical structure database. It retrieves data matching a molecular substructure pattern but does not create, modify, delete, or execute external operations. The tool is analogous to a SELECT query in SQL.
From the tool's definition Tool description states 'Run RDKit substructure search over indexed RDF molfile structures' — this is a search operation that queries and retrieves matching chemical structures without modifying data.
Attacks that exploit this kind of access
Run RDKit substructure search over indexed RDF molfile structures. It is categorised as a Read tool in the Scifinder Route MCP Server, which means it retrieves data without modifying state.
Register the Scifinder Route MCP server in PolicyLayer and add a rule for substructure_search_structures: 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 Scifinder Route. Nothing to install.
substructure_search_structures 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 substructure_search_structures 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 substructure_search_structures. 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.
substructure_search_structures is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). 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 →