Rename a Markdown (.md) note inside Notes or a category.
AI agents use rename_note to create or update resources in Nextcloud Notes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nextcloud Notes environment.
Renaming a note creates or modifies data reversibly, fitting the Write category. It is not Destructive because the original content is preserved and the action can be undone by renaming again. Severity is medium because misuse could cause confusion or operational disruption in a notes system, but the impact is limited to metadata changes without data loss or access to sensitive operations.
From the tool's definition Tool modifies note metadata by renaming files ("Rename a Markdown (.md) note"). The operation is reversible—a note can be renamed again to its original name or any other name.
Attacks that exploit this kind of access
Rename a Markdown (.md) note inside Notes or a category. It is categorised as a Write tool in the Nextcloud Notes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nextcloud Notes MCP server in PolicyLayer and add a rule for rename_note: 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 Nextcloud Notes. Nothing to install.
rename_note 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_note 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_note. 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_note is provided by the Nextcloud Notes MCP server (rncz/nextcloud-notes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →