set_file_tags
Set personal tags on a file or folder in Nextcloud. Replaces all existing personal tags. Use an empty array to clear all tags.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/set-file-tags.md
What set_file_tags does on AIquila — Nextcloud MCP Server
AI agents use set_file_tags 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.
Why set_file_tags is rated Medium
This tool modifies file metadata (tags) in a reversible manner. Tags can be added, replaced, or cleared without deleting underlying file content. It qualifies as Write rather than Read (retrieves data) or Destructive (irreversible deletion). The reversibility and limited scope (metadata only) justify medium severity—an agent could disrupt organization/workflows but not cause data loss or financial harm.
From the tool's definition Tool sets/replaces personal tags on files or folders. Description explicitly states: 'Replaces all existing personal tags' and 'Use an empty array to clear all tags.' This is a modification operation that alters metadata.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_file_tags 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 set_file_tags, this is the rule to start with:
set_file_tags 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 set_file_tags call is checked against it from then on.
Questions about set_file_tags
Set personal tags on a file or folder in Nextcloud. Replaces all existing personal tags. Use an empty array to clear all tags. 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.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for set_file_tags: 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.
set_file_tags 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 set_file_tags 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 set_file_tags. 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.
set_file_tags 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