calendars_edit_appointment

Update Appointment

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-edit-appointment.md

WHAT IT DOES

What calendars_edit_appointment does on Ghl

AI agents use calendars_edit_appointment 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
`rrule`	string	—	RRULE as per the iCalendar (RFC 5545) specification for recurring events. DTSTART is not required, instance ids are calculated on the basis of startTime of the
`title`	string	—	Title
`address`	string	—	Appointment Address
`endTime`	string	—	End Time
`eventId`	string	Yes	Event Id or Instance id. For recurring appointments send masterEventId to modify original series.
`toNotify`	boolean	—	If set to false, the automations will not run
`startTime`	string	—	Start Time
`calendarId`	string	—	Calendar Id
`description`	string	—	Appointment Description
`assignedUserId`	string	—	Assigned User Id
`ignoreDateRange`	boolean	—	If set to true, the minimum scheduling notice and date range would be ignored
`appointmentStatus`	string	—

Parameters from the server's own tool schema.

RISK

Why calendars_edit_appointment is rated Medium

An AI agent can call calendars_edit_appointment faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs calendars_edit_appointment 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 calendars_edit_appointment, this is the rule to start with:

calendars_edit_appointment Rate-limited

calendars_edit_appointment 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendars_edit_appointment": {
      "limits": [
        {
          "counter": "calendars_edit_appointment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every calendars_edit_appointment call is checked against it from then on.

FAQ

Questions about calendars_edit_appointment

What does the calendars_edit_appointment tool do? +

Update 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.

What parameters does calendars_edit_appointment accept? +

calendars_edit_appointment accepts 12 parameters: rrule, title, address, endTime, eventId, toNotify, startTime, calendarId, description, assignedUserId, ignoreDateRange, appointmentStatus. Required: eventId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calendars_edit_appointment? +

Register the Ghl MCP server in PolicyLayer and add a rule for calendars_edit_appointment: 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.

What risk level is calendars_edit_appointment? +

calendars_edit_appointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calendars_edit_appointment? +

Yes. Add a rate_limit block to the calendars_edit_appointment 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.

How do I block calendars_edit_appointment completely? +

Set action: deny in the PolicyLayer policy for calendars_edit_appointment. 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.

What MCP server provides calendars_edit_appointment? +

calendars_edit_appointment 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →