reprocess_failed_documents · LightRAG MCP Server MCP

WHAT IT DOES

What reprocess_failed_documents does on LightRAG MCP Server

AI agents invoke reprocess_failed_documents to trigger actions in LightRAG MCP Server. 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 reprocess_failed_documents needs a policy

This tool triggers reprocessing of documents that previously failed or are pending, which executes an external operation (document ingestion/processing pipeline). It doesn't simply read data, nor does it irreversibly delete anything — it re-runs a processing workflow, making Execute the most appropriate category. Misuse could cause unintended re-ingestion or pipeline load, hence medium severity.

From the tool's definition Reprocess failed and pending documents

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reprocess_failed_documents Rate-limited

reprocess_failed_documents 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": {
    "reprocess_failed_documents": {
      "limits": [
        {
          "counter": "reprocess_failed_documents_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 LightRAG MCP Server, so you can run agents against it safely.

FAQ

Questions about reprocess_failed_documents

What does the reprocess_failed_documents tool do? +

Reprocess failed and pending documents. It is categorised as a Execute tool in the LightRAG MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reprocess_failed_documents? +

Register the LightRAG MCP Server MCP server in PolicyLayer and add a rule for reprocess_failed_documents: 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 LightRAG MCP Server. Nothing to install.

What risk level is reprocess_failed_documents? +

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

Can I rate-limit reprocess_failed_documents? +

Yes. Add a rate_limit block to the reprocess_failed_documents 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 reprocess_failed_documents completely? +

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

reprocess_failed_documents is provided by the LightRAG MCP Server MCP server (lalitsuryan/lightragmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.