delete_contact
Delete a contact from a Nextcloud address book by UID. This action is irreversible.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/delete-contact.md
What delete_contact does on AIquila — Nextcloud MCP Server
AI agents call delete_contact 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 |
|---|---|---|---|
uid | string | Yes | The UID of the contact to delete |
addressBookName | string | — | The address book name (default: 'contacts') |
Parameters from the server's own tool schema.
Why delete_contact is rated Critical
This tool permanently removes contact data from a Nextcloud address book with no undo capability. The irreversible nature of deletion places it in the Destructive category rather than Write. Severity is high because an AI agent misuse could result in loss of important contact information for users, though the blast radius is typically limited to individual contacts rather than system-wide data.
From the tool's definition Tool name is 'delete_contact' and description explicitly states 'Delete a contact' and 'This action is irreversible.' The description uses 'irreversible' which directly invokes the Destructive category definition.
Attacks that exploit this kind of access
The rule that runs delete_contact 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 delete_contact, this is the rule to start with:
delete_contact 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 delete_contact call is checked against it from then on.
Questions about delete_contact
Delete a contact from a Nextcloud address book by UID. This action is irreversible. 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.
delete_contact accepts 2 parameters: uid, addressBookName. Required: uid. 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 delete_contact: 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.
delete_contact 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 delete_contact 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 delete_contact. 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.
delete_contact 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