This record as markdown: /tools/ghl/delete-appointment-note.md
What delete_appointment_note does on Ghl
AI agents call delete_appointment_note 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 |
|---|---|---|---|
noteId | string | Yes | Note ID |
appointmentId | string | Yes | Appointment ID |
Parameters from the server's own tool schema.
Why delete_appointment_note is rated Critical
This tool permanently removes appointment note data with no stated undo capability. Deletion of business records is irreversible and fits the Destructive category. Severity is high because loss of appointment notes could impact business operations, compliance, and customer relationships, though the blast radius is narrower than system-wide data destruction.
From the tool's definition Tool name explicitly states 'delete_appointment_note' and description confirms 'Delete an appointment note' — direct deletion action that irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs delete_appointment_note 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_appointment_note, this is the rule to start with:
delete_appointment_note 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_appointment_note call is checked against it from then on.
Questions about delete_appointment_note
Delete an appointment note. 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_appointment_note accepts 2 parameters: noteId, appointmentId. Required: noteId, appointmentId. 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_appointment_note: 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_appointment_note 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_appointment_note 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_appointment_note. 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_appointment_note 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