This record as markdown: /tools/ghl/delete-contact-task.md
What delete_contact_task does on Ghl
AI agents call delete_contact_task to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | Yes | Task ID |
contactId | string | Yes | Contact ID |
Parameters from the server's own tool schema.
Why delete_contact_task is rated Critical
This tool permanently removes task data associated with a contact without reversibility. While the blast radius is limited to a single contact's task (not system-wide or financial), deletion of work items can disrupt workflows, lose information, and prevent task completion. Classified as Destructive (not Write) because the operation cannot be undone.
From the tool's definition Tool name contains 'delete_task' and description states 'Delete a task for a contact' — explicit irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_contact_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_contact_task, this is the rule to start with:
delete_contact_task 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 Ghl, apply this rule, and every delete_contact_task call is checked against it from then on.
Questions about delete_contact_task
Delete a task for a contact. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_contact_task accepts 2 parameters: taskId, contactId. Required: taskId, contactId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for delete_contact_task: 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 Ghl. Nothing to install.
delete_contact_task 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_task 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_task. 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_task is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue