Return one export batch, linked documents, confidence, and merge explanation.
AI agents call get_export_batch 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 returns existing data (an export batch, linked documents, metadata) without creating, modifying, deleting, or executing any external operations. It is a pure read operation with no blast radius if misused—at worst, an agent could repeatedly fetch the same batch, consuming resources, but no data integrity or system state is compromised.
From the tool's definition Tool name 'get_export_batch' and description 'Return one export batch, linked documents, confidence, and merge explanation' indicate data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Return one export batch, linked documents, confidence, and merge explanation. 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 get_export_batch: 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.
get_export_batch 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 get_export_batch 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 get_export_batch. 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.
get_export_batch 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 →