Cancel an existing appointment
AI agents call cancel_appointment to permanently remove resources in Google Calendar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an appointment is an irreversible action in practice: the time slot is released, notifications may be sent to patients and providers, and the booking is permanently invalidated. This aligns with the Destructive category (irreversible deletion/overwrite).
From the tool's definition "Cancel an existing appointment" — cancellation removes/invalidates the appointment, which is not easily reversible once the patient/provider has been notified
Attacks that exploit this kind of access
Cancel an existing appointment. It is categorised as a Destructive tool in the Google Calendar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for cancel_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 Google Calendar MCP Server. Nothing to install.
cancel_appointment 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 cancel_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.
Set action: deny in the PolicyLayer policy for cancel_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.
cancel_appointment is provided by the Google Calendar MCP Server MCP server (roelovanheeren/final-gc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →