post_document · Paperless-NGX MCP Server MCP: Risk & Policy

WHAT IT DOES

What post_document does on Paperless-NGX MCP Server

AI agents use post_document to create or update resources in Paperless-NGX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paperless-NGX MCP Server environment.

WHY IT NEEDS A POLICY

Why post_document needs a policy

This tool creates new data (documents) in the system, which is a write operation. It is not destructive since uploads are reversible. It is not execute because it does not run code or arbitrary commands—it simply processes files through the system's standard OCR and indexing pipeline.

From the tool's definition Tool description states 'Upload a new document' and 'Supports PDF, images (PNG/JPG/TIFF), and text files.' The tool creates new document records in Paperless-NGX with metadata, which are reversible operations (documents can be deleted).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

post_document Rate-limited

post_document 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": {
    "post_document": {
      "limits": [
        {
          "counter": "post_document_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 Paperless-NGX MCP Server, so you can run agents against it safely.

FAQ

Questions about post_document

What does the post_document tool do? +

Upload a new document to Paperless-NGX with metadata. Supports PDF, images (PNG/JPG/TIFF), and text files. Automatically processes for OCR and indexing. It is categorised as a Write tool in the Paperless-NGX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on post_document? +

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

What risk level is post_document? +

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

Can I rate-limit post_document? +

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

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

post_document is provided by the Paperless-NGX MCP Server MCP server (mephistojb/paperless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.