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).
This record as markdown: /tools/vipcasso-mcp/deleteconciergelead.md
What deleteConciergeLead does on Vipcasso
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | |
files | array | — | |
query | object | — | |
fields | object | — | |
path_params | object | — |
Parameters from the server's own tool schema.
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 signalsAccepts file system path (files[].filename) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs deleteConciergeLead safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vipcasso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteConciergeLead, this is the rule to start with:
deleteConciergeLead 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 Vipcasso, apply this rule, and every deleteConciergeLead call is checked against it from then on.
Questions about 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). It is categorised as a Destructive tool in the Vipcasso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteConciergeLead accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.
Register the Vipcasso MCP server in PolicyLayer and add a rule for deleteConciergeLead: 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 Vipcasso. Nothing to install.
deleteConciergeLead 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 deleteConciergeLead 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 deleteConciergeLead. 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.
deleteConciergeLead is provided by the Vipcasso MCP server (@vipcasso/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vipcasso, and thousands of servers like it.
Across the catalogue