List recent parse jobs, optionally filtered by status.
AI agents call list_parse_jobs 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 information about parse jobs (their status, history, etc.). It performs no creation, modification, deletion, or execution of external operations. Filtering is a read-only query operation. The low severity reflects minimal blast radius—an AI agent misusing this to list jobs cannot cause harm beyond information disclosure.
From the tool's definition Tool name 'list_parse_jobs' and description 'List recent parse jobs, optionally filtered by status' indicate a retrieval operation with no data modification. The verb 'list' is a classic read operation that queries existing state without side effects.
Attacks that exploit this kind of access
List recent parse jobs, optionally filtered by status. 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_parse_jobs: 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_parse_jobs 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_parse_jobs 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_parse_jobs. 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_parse_jobs 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 →