List CAS reaction-level evidence links between RDF records and PDF pages.
AI agents call list_reaction_links 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 retrieves and displays existing reaction-level evidence links between RDF records and PDF pages. It performs no modifications, deletions, or side effects. The operation is fundamentally a read query of an index or database. The low severity reflects minimal blast radius if misused—an agent listing links cannot cause data loss or unauthorized actions.
From the tool's definition Tool name 'list_reaction_links' and description 'List CAS reaction-level evidence links' indicate a retrieval/query operation. The verb 'list' is a classic Read operation that queries and returns data without modifying state.
Attacks that exploit this kind of access
List CAS reaction-level evidence links between RDF records and PDF pages. 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_reaction_links: 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_reaction_links 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_reaction_links 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_reaction_links. 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_reaction_links 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 →