Critical Risk →

delete_tag

Permanently delete a tag from the system. This removes the tag from all documents that currently use it. Use with caution as this action cannot be undone.

How to control delete_tag ↓

AI agents call delete_tag to permanently remove resources in Paperless-NGX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes metadata (tags) from the system and cascades the deletion to all associated documents. While not as catastrophic as deleting entire documents, it permanently removes organizational information that cannot be recovered. The explicit warning about being unable to undo the action confirms destructive semantics.

From the tool's definition Tool description explicitly states 'Permanently delete a tag from the system' and 'This removes the tag from all documents that currently use it' and warns 'this action cannot be undone.' The word 'Permanently' combined with 'cannot be undone' indicates…

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access delete_tag gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Paperless-NGX MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_tag:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_tag"
  ]
}

delete_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Paperless-NGX MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_tag tool do? +

Permanently delete a tag from the system. This removes the tag from all documents that currently use it. Use with caution as this action cannot be undone. It is categorised as a Destructive tool in the Paperless-NGX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_tag? +

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

delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_tag? +

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

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

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

Enforce policy on every Paperless-NGX MCP Server tool call.

Deterministic rules across all 16 Paperless-NGX MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 Paperless-NGX MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.