This record as markdown: /tools/ghl/get-appointment-notes.md
What get_appointment_notes does on Ghl
AI agents call get_appointment_notes to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of notes to return |
offset | number | — | Number of notes to skip |
appointmentId | string | Yes | Appointment ID |
Parameters from the server's own tool schema.
Why get_appointment_notes is rated Low
This tool retrieves existing appointment notes. It performs a query operation that reads data without creating, modifying, deleting, or executing code. The verb 'Get' and the retrieval-focused description confirm this is a Read category tool with minimal risk.
From the tool's definition Tool name 'get_appointment_notes' and description 'Get notes for an appointment' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_appointment_notes 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 get_appointment_notes, this is the rule to start with:
get_appointment_notes is read-only, so it stays allowed. 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 get_appointment_notes call is checked against it from then on.
Questions about get_appointment_notes
Get notes for an appointment. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_appointment_notes accepts 3 parameters: limit, offset, appointmentId. Required: 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 get_appointment_notes: 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.
get_appointment_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_appointment_notes 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 get_appointment_notes. 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.
get_appointment_notes 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