remove_project_path
Remove a file or directory path from an AIquila project.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/remove-project-path.md
What remove_project_path does on AIquila — Nextcloud MCP Server
AI agents call remove_project_path to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Project ID |
pathId | number | Yes | Path ID to remove |
Parameters from the server's own tool schema.
Why remove_project_path is rated Critical
Removing files or directories is a destructive operation that cannot be undone without restore mechanisms. This action permanently deletes data associations within the project. While severity is not 'critical' (as it affects a specific project scope rather than system-wide data), the irreversible nature of deletion makes this Destructive category rather than Write.
From the tool's definition Tool name contains 'remove' and description states 'Remove a file or directory path from an AIquila project.' The verb 'remove' combined with 'file or directory' indicates irreversible deletion of filesystem resources.
Attacks that exploit this kind of access
The rule that runs remove_project_path 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 remove_project_path, this is the rule to start with:
remove_project_path is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every remove_project_path call is checked against it from then on.
Questions about remove_project_path
Remove a file or directory path from an AIquila project. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_project_path accepts 2 parameters: id, pathId. Required: id, pathId. 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 remove_project_path: 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.
remove_project_path is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_project_path 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 remove_project_path. 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.
remove_project_path 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.
Across the catalogue