This record as markdown: /tools/ghl/create-appointment-note.md
What create_appointment_note does on Ghl
AI agents use create_appointment_note to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Note content |
userId | string | — | User ID creating the note |
appointmentId | string | Yes | Appointment ID |
Parameters from the server's own tool schema.
Why create_appointment_note is rated Medium
This tool creates a new note associated with an appointment, which is a reversible data modification. It does not execute arbitrary code, delete data, or move money. The medium severity reflects that misuse could create unwanted appointment notes in a CRM system affecting customer records and workflows, but the impact is limited to note data and can be corrected by deletion.
From the tool's definition Tool name 'create_appointment_note' and description 'Create a note for an appointment' indicate data creation/modification. The verb 'create' and context of a CRM (GoHighLevel) system establish this as a write operation that adds a note record.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_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 create_appointment_note, this is the rule to start with:
create_appointment_note stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every create_appointment_note call is checked against it from then on.
Questions about create_appointment_note
Create a note for an appointment. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_appointment_note accepts 3 parameters: body, userId, appointmentId. Required: body, 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 create_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.
create_appointment_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue