This record as markdown: /tools/ghl/delete-object-record.md
What delete_object_record does on Ghl
AI agents call delete_object_record 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 |
|---|---|---|---|
recordId | string | Yes | ID of the record to delete |
schemaKey | string | Yes | Schema key of the object |
Parameters from the server's own tool schema.
Why delete_object_record is rated Critical
This tool performs permanent deletion of data records without reversibility. It falls into the Destructive category because deletion cannot be undone and represents the highest severity risk when misused by an AI agent, which could inadvertently wipe out critical business data, customer records, or custom object entries in GoHighLevel's CRM system.
From the tool's definition Tool name 'delete_object_record' with description 'Delete a record from a custom or standard object' explicitly performs irreversible deletion of data records.
Attacks that exploit this kind of access
The rule that runs delete_object_record 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_object_record, this is the rule to start with:
delete_object_record 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_object_record call is checked against it from then on.
Questions about delete_object_record
Delete a record from a custom or standard object. 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_object_record accepts 2 parameters: recordId, schemaKey. Required: recordId, schemaKey. 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_object_record: 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_object_record 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_object_record 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_object_record. 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_object_record 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