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.
This tool creates or modifies data reversibly (metadata tags) in the document management system. While it affects organizational structures, the changes can be undone through subsequent updates or reversions. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or irreversibly destroy information.
From the tool's definition Tool name 'update_tag' and description 'Modify an existing tag' indicate reversible modification of metadata. The action is a write operation that changes tag properties without deletion or destruction.
Documented attack patterns abuse exactly the kind of access update_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 update_tag:
{
"version": "1",
"default": "deny",
"tools": {
"update_tag": {
"limits": [
{
"counter": "update_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
update_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_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.
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.