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

WHAT IT DOES

What update_tag does on Paperless-NGX MCP Server

AI agents use update_tag 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 update_tag needs a policy

This tool creates or modifies data in a reversible manner. Updating a tag affects metadata and organization of documents within the Paperless-NGX system, but the change can be undone by updating the tag again. It is not destructive (no deletion), not financial, and not execute/code-running.

From the tool's definition Tool name 'update_tag' and description 'Modify an existing tag' indicate reversible modification of data. The action changes tag properties but does not delete or destroy data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tag Rate-limited

update_tag 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": {
    "update_tag": {
      "limits": [
        {
          "counter": "update_tag_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 update_tag

What does the update_tag tool do? +

Modify an existing tag. 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 update_tag? +

Register the Paperless-NGX MCP Server MCP server in PolicyLayer and add a rule for update_tag: 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 update_tag? +

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

Can I rate-limit update_tag? +

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

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

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