rename_feed

Rename a feed.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/rename-feed.md

WHAT IT DOES

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.

RISK

Why rename_feed is rated Medium

This is a Write operation because it modifies data (the feed's name) in a reversible manner. Renaming can be undone by renaming again to the original name. It is not destructive because the feed and its contents remain intact.

From the tool's definition The tool 'rename_feed' modifies an existing feed by changing its name. The description explicitly states it performs a rename operation, which is a reversible update to feed metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_feed": {
      "limits": [
        {
          "counter": "rename_feed_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about rename_feed

What does the rename_feed tool do? +

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.

How do I enforce a policy on rename_feed? +

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.

What risk level is rename_feed? +

rename_feed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_feed? +

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.

How do I block rename_feed completely? +

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.

What MCP server provides rename_feed? +

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.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 295 AIquila — Nextcloud MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →