# deleteConciergeLead

Erase one lead (Law 25 / GDPR erasure, or a test): its personal details are blanked, webhook copies reduced to the id, and the questions its conversation gave to FAQ suggestions are deleted (open suggestions left without two visitors behind them go too).

Agent View of the PolicyLayer registry record for `deleteConciergeLead`. HTML page: https://policylayer.com/tools/vipcasso-mcp/deleteconciergelead

## Facts

- Tool: `deleteConciergeLead`
- Server: Vipcasso (`@vipcasso/mcp`) — https://policylayer.com/tools/vipcasso-mcp.md
- Install: `npx -y @vipcasso/mcp`
- Homepage: https://www.npmjs.com/package/@vipcasso/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 5
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `body` | object | no |  |
| `files` | array | no |  |
| `query` | object | no |  |
| `fields` | object | no |  |
| `path_params` | object | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deleteConciergeLead",
    "arguments": {}
  }
}
```

## Why deleteConciergeLead is rated Critical

An AI agent that decides to call deleteConciergeLead doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Vipcasso is gone. There is no undo for destructive operations.

Risk signals: Accepts file system path (files[].filename) · Accepts raw HTML/template content (body)

## Use case

AI agents call deleteConciergeLead to permanently remove resources in Vipcasso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Vipcasso:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteConciergeLead"
  ]
}
```

## Other tools on Vipcasso (232)

- `clearManagedAccountAiPrice` — Destructive — https://policylayer.com/tools/vipcasso-mcp/clearmanagedaccountaiprice.md
- `clearPlatformRateCardItem` — Destructive — https://policylayer.com/tools/vipcasso-mcp/clearplatformratecarditem.md
- `deleteAsset` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteasset.md
- `deleteCollection` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecollection.md
- `deleteCollectionRule` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecollectionrule.md
- `deleteConciergePersona` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteconciergepersona.md
- `deleteConnector` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteconnector.md
- `deleteContentLink` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecontentlink.md
- `deleteContentObject` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecontentobject.md
- `deletePage` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletepage.md
- `deleteSurface` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletesurface.md
- `endAccountAccess` — Destructive — https://policylayer.com/tools/vipcasso-mcp/endaccountaccess.md
- `removeCollectionMember` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removecollectionmember.md
- `removeLookFavorite` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removelookfavorite.md
- `removeSiteDomain` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removesitedomain.md
- `removeTeammate` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removeteammate.md
- `revokeApiKey` — Destructive — https://policylayer.com/tools/vipcasso-mcp/revokeapikey.md
- `revokeCollectionShare` — Destructive — https://policylayer.com/tools/vipcasso-mcp/revokecollectionshare.md
- `unpublishCollection` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishcollection.md
- `unpublishPage` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishpage.md
- `unpublishSurface` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishsurface.md
- `executeOperator` — Execute — https://policylayer.com/tools/vipcasso-mcp/executeoperator.md
- `quoteOperatorRun` — Execute — https://policylayer.com/tools/vipcasso-mcp/quoteoperatorrun.md
- `startDirector` — Execute — https://policylayer.com/tools/vipcasso-mcp/startdirector.md
- `startIngestionJob` — Execute — https://policylayer.com/tools/vipcasso-mcp/startingestionjob.md
- `transformAsset` — Execute — https://policylayer.com/tools/vipcasso-mcp/transformasset.md
- `analyzeAsset` — Read — https://policylayer.com/tools/vipcasso-mcp/analyzeasset.md
- `auditionDirectorVoices` — Read — https://policylayer.com/tools/vipcasso-mcp/auditiondirectorvoices.md
- `autoGroupCollections` — Read — https://policylayer.com/tools/vipcasso-mcp/autogroupcollections.md
- `catalogueAssets` — Read — https://policylayer.com/tools/vipcasso-mcp/catalogueassets.md
- …and 202 more: https://policylayer.com/tools/vipcasso-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=vipcasso-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/vipcasso-mcp
