This record as markdown: /tools/aiwerk-mcp-server-ghl/conversation-ai-delete-action.md
What conversation_ai_delete_action does on Ghl
AI agents call conversation_ai_delete_action 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 |
|---|---|---|---|
agentId | string | Yes | |
actionId | string | Yes | The unique identifier of the action ID Attached to the agent |
Parameters from the server's own tool schema.
Why conversation_ai_delete_action is rated Critical
An AI agent that decides to call conversation_ai_delete_action doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs conversation_ai_delete_action 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 conversation_ai_delete_action, this is the rule to start with:
conversation_ai_delete_action 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 conversation_ai_delete_action call is checked against it from then on.
Questions about conversation_ai_delete_action
Remove Action from Agent. 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.
conversation_ai_delete_action accepts 2 parameters: agentId, actionId. Required: agentId, actionId. 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 conversation_ai_delete_action: 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.
conversation_ai_delete_action 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 conversation_ai_delete_action 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 conversation_ai_delete_action. 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.
conversation_ai_delete_action is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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