assign_system_tag
Assign a system tag to a file by file ID and tag ID. Use get_file_info to obtain the file ID.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/assign-system-tag.md
What assign_system_tag does on AIquila — Nextcloud MCP Server
AI agents use assign_system_tag to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tagId | number | Yes | The system tag ID to assign |
fileId | number | Yes | The Nextcloud file ID |
Parameters from the server's own tool schema.
Why assign_system_tag is rated Medium
The tool modifies file metadata (assigns a tag) reversibly without deleting or destroying data. This is a Write operation with medium severity because an AI agent could misuse tag assignments to mislabel files at scale, affecting file organization and access control, but the change is reversible through tag removal.
From the tool's definition Tool description states 'Assign a system tag to a file by file ID and tag ID', which is a modification operation that adds metadata to an existing file.
Attacks that exploit this kind of access
The rule that runs assign_system_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assign_system_tag, this is the rule to start with:
assign_system_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every assign_system_tag call is checked against it from then on.
Questions about assign_system_tag
Assign a system tag to a file by file ID and tag ID. Use get_file_info to obtain the file ID. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
assign_system_tag accepts 2 parameters: tagId, fileId. Required: tagId, fileId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for assign_system_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 AIquila — Nextcloud MCP Server. Nothing to install.
assign_system_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 assign_system_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 assign_system_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.
assign_system_tag is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue