retry_parse_job · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What retry_parse_job does on Scifinder Route

AI agents invoke retry_parse_job to trigger actions in Scifinder Route. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why retry_parse_job needs a policy

The tool executes an operation (job retry/requeue) whose outcome is not immediately reversible by the user and depends on external job processing logic. It is not a simple Read (no data retrieval), not Write in the straightforward sense (no direct data creation/modification by the user), and not Destructive (the retry itself doesn't delete data).

From the tool's definition 'Retry a failed or completed parse job by moving it back to the durable queue' — this tool triggers a background job that processes and parses synthesis routes from SciFinder exports. The effects depend on which job is retried and the data it operates on.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_parse_job Rate-limited

retry_parse_job stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "retry_parse_job": {
      "limits": [
        {
          "counter": "retry_parse_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Scifinder Route, so you can run agents against it safely.

FAQ

Questions about retry_parse_job

What does the retry_parse_job tool do? +

Retry a failed or completed parse job by moving it back to the durable queue. It is categorised as a Execute tool in the Scifinder Route MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_parse_job? +

Register the Scifinder Route MCP server in PolicyLayer and add a rule for retry_parse_job: 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.

What risk level is retry_parse_job? +

retry_parse_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retry_parse_job? +

Yes. Add a rate_limit block to the retry_parse_job 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.

How do I block retry_parse_job completely? +

Set action: deny in the PolicyLayer policy for retry_parse_job. 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.

What MCP server provides retry_parse_job? +

retry_parse_job 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.