Search extracted reaction steps by text and structured condition filters.
AI agents call search_reaction_steps 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 performs a search/query operation over a local database of reaction synthesis routes. It retrieves data based on text and condition filters but does not create, modify, delete, or execute code. The search functionality is read-only with no side effects on the underlying data or external systems. The severity is low as misuse would only expose information already indexed in the server.
From the tool's definition Tool name 'search_reaction_steps' combined with description 'Search extracted reaction steps by text and structured condition filters' indicates retrieval and querying of existing data without modification or deletion.
Attacks that exploit this kind of access
Search extracted reaction steps by text and structured condition filters. 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 search_reaction_steps: 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.
search_reaction_steps 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_reaction_steps 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_reaction_steps. 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_reaction_steps 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 →