List indexed SciFinder RDF reaction records with scheme/step metadata.
AI agents call list_rdf_reactions 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.
This tool queries and returns existing reaction record data from a local SciFinder database index. It has no side effects, does not modify or delete data, and does not execute arbitrary code or trigger external operations.
From the tool's definition Tool name is 'list_rdf_reactions' and description states it 'List indexed SciFinder RDF reaction records' — a retrieval operation with no modification or deletion. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
List indexed SciFinder RDF reaction records with scheme/step metadata. 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 list_rdf_reactions: 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.
list_rdf_reactions 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 list_rdf_reactions 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 list_rdf_reactions. 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.
list_rdf_reactions 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 →