Lösche einen Termin aus Daylite.
AI agents call daylite_delete_appointment to permanently remove resources in Daylite Claude Connector — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of calendar appointments cannot be undone and constitutes irreversible data loss. This qualifies as Destructive rather than Write. The high severity reflects the potential business impact of accidentally deleting important meetings or commitments through AI misuse.
From the tool's definition Tool name contains 'delete_appointment' and description states 'Lösche einen Termin aus Daylite' (Delete an appointment from Daylite). This is an irreversible deletion operation.
Attacks that exploit this kind of access
Lösche einen Termin aus Daylite. It is categorised as a Destructive tool in the Daylite Claude Connector MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_delete_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 Daylite Claude Connector. Nothing to install.
daylite_delete_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 daylite_delete_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 daylite_delete_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.
daylite_delete_appointment is provided by the Daylite Claude Connector MCP server (wimwoeber/daylite-claude-connector). 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 →