move_feed
Move a feed into a different folder.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/move-feed.md
What move_feed does on AIquila — Nextcloud MCP Server
AI agents use move_feed 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 |
|---|---|---|---|
feedId | number | Yes | The feed ID to move |
folderId | number | Yes | Destination folder ID (0 for root) |
Parameters from the server's own tool schema.
Why move_feed is rated Medium
Moving a feed between folders is a write operation that changes metadata (folder assignment) but does not delete, destroy, or permanently alter the feed itself. The action is reversible—the feed can be moved back. It does not execute arbitrary code, trigger external operations, or involve financial transactions.
From the tool's definition The tool description states it "Move[s] a feed into a different folder," which modifies the organization/location of data (a feed resource) without deleting it. This is a reversible structural change.
Attacks that exploit this kind of access
The rule that runs move_feed 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 move_feed, this is the rule to start with:
move_feed 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 move_feed call is checked against it from then on.
Questions about move_feed
Move a feed into a different folder. 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.
move_feed accepts 2 parameters: feedId, folderId. Required: feedId, folderId. 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 move_feed: 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.
move_feed 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 move_feed 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 move_feed. 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.
move_feed 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