daylite_update_appointment · Daylite Claude Connector MCP

WHAT IT DOES

What daylite_update_appointment does on Daylite Claude Connector

AI agents use daylite_update_appointment to create or update resources in Daylite Claude Connector — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Daylite Claude Connector environment.

WHY IT NEEDS A POLICY

Why daylite_update_appointment needs a policy

This tool modifies existing appointment records in the Daylite CRM system reversibly. It is Write rather than Execute because it directly changes data structures (appointment fields) rather than triggering complex conditional logic or external operations. It is not Destructive because updates are reversible and the original data is not erased.

From the tool's definition Tool name 'daylite_update_appointment' and description 'Aktualisiere einen bestehenden Daylite-Termin' (Update an existing Daylite appointment) indicate modification of existing calendar data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

daylite_update_appointment Rate-limited

daylite_update_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": {
    "daylite_update_appointment": {
      "limits": [
        {
          "counter": "daylite_update_appointment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Daylite Claude Connector, so you can run agents against it safely.

FAQ

Questions about daylite_update_appointment

What does the daylite_update_appointment tool do? +

Aktualisiere einen bestehenden Daylite-Termin. It is categorised as a Write tool in the Daylite Claude Connector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on daylite_update_appointment? +

Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_update_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.

What risk level is daylite_update_appointment? +

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

Can I rate-limit daylite_update_appointment? +

Yes. Add a rate_limit block to the daylite_update_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 daylite_update_appointment completely? +

Set action: deny in the PolicyLayer policy for daylite_update_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 daylite_update_appointment? +

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