update_project
Update an AIquila project. Only provided fields are updated.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-project.md
What update_project does on AIquila — Nextcloud MCP Server
AI agents use update_project 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 |
|---|---|---|---|
id | number | Yes | Project ID |
title | string | — | New project title |
description | string | — | New project description |
systemPrompt | string | — | New system prompt for conversations using this project |
Parameters from the server's own tool schema.
Why update_project is rated Medium
The tool modifies project data without deleting it. Updates are reversible through further modifications. Severity is medium because unauthorized project updates could affect team workflows, data integrity, or access controls within Nextcloud/AIquila, but the impact is typically localized to that project rather than system-wide or destructive.
From the tool's definition Tool description states 'Update an AIquila project' with selective field updates ('Only provided fields are updated'). This indicates modification of existing data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_project 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 update_project, this is the rule to start with:
update_project 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 update_project call is checked against it from then on.
Questions about update_project
Update an AIquila project. Only provided fields are updated. 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.
update_project accepts 4 parameters: id, title, description, systemPrompt. Required: id. 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 update_project: 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.
update_project 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 update_project 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 update_project. 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.
update_project 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