unlink_document_from_batch · Scifinder Route MCP

WHAT IT DOES

What unlink_document_from_batch does on Scifinder Route

AI agents use unlink_document_from_batch 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.

WHY IT NEEDS A POLICY

Why unlink_document_from_batch needs a policy

This tool modifies the association between a document and a batch (removing a link), which is a reversible write operation. It does not permanently delete the document itself, and the audit reason implies traceability. The action is corrective/administrative in nature. Severity is medium because misuse could disrupt batch integrity or cause data linkage issues.

From the tool's definition Remove an incorrectly merged document from an export batch with an audit reason

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unlink_document_from_batch Rate-limited

unlink_document_from_batch stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unlink_document_from_batch": {
      "limits": [
        {
          "counter": "unlink_document_from_batch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 unlink_document_from_batch

What does the unlink_document_from_batch tool do? +

Remove an incorrectly merged document from an export batch with an audit reason. 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.

How do I enforce a policy on unlink_document_from_batch? +

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

What risk level is unlink_document_from_batch? +

unlink_document_from_batch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unlink_document_from_batch? +

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

How do I block unlink_document_from_batch completely? +

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

What MCP server provides unlink_document_from_batch? +

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