This record as markdown: /tools/aiquila-nextcloud-mcp-server/rename-feed.md
What rename_feed does on AIquila — Nextcloud MCP Server
AI agents use rename_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 rename |
feedTitle | string | Yes | The new feed title |
Parameters from the server's own tool schema.
Why rename_feed is rated Medium
Renaming a feed modifies feed properties reversibly without deleting data or causing irreversible changes. This is a standard write operation. Severity is low because feed metadata changes have minimal blast radius and are easily undone by renaming again.
From the tool's definition Tool name 'rename_feed' and description 'Rename a feed' indicate modification of existing data (feed metadata).
Attacks that exploit this kind of access
The rule that runs rename_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 rename_feed, this is the rule to start with:
rename_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 rename_feed call is checked against it from then on.
Questions about rename_feed
Rename a feed. 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.
rename_feed accepts 2 parameters: feedId, feedTitle. Required: feedId, feedTitle. 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 rename_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.
rename_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 rename_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 rename_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.
rename_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