Confirm a candidate reaction link from PDF evidence block rules.
AI agents use confirm_reaction_link to create or update resources in Scifinder Route — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scifinder Route environment.
Confirming a candidate link creates or finalizes a relationship in the database. This is a reversible write operation (the link could presumably be deleted or unconfirmed), not inherently destructive. Severity is medium because misconfirming links could corrupt reaction-synthesis data, but the action is not irreversible.
From the tool's definition "Confirm a candidate reaction link" — confirms/commits a pending link between a reaction and PDF evidence
Attacks that exploit this kind of access
Confirm a candidate reaction link from PDF evidence block rules. It is categorised as a Write tool in the Scifinder Route MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scifinder Route MCP server in PolicyLayer and add a rule for confirm_reaction_link: 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.
confirm_reaction_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the confirm_reaction_link 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 confirm_reaction_link. 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.
confirm_reaction_link 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 →