Rufe einen einzelnen Daylite-Termin per ID ab.
AI agents call daylite_get_appointment to retrieve information from Daylite Claude Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single appointment record from Daylite CRM by its ID. It performs a read-only query operation with no capability to modify, delete, or execute actions. The German description confirms it is a retrieval ('Rufe...ab') operation. The blast radius of misuse is minimal—an agent could only access an appointment record that already exists, with no unintended side effects on the system.
From the tool's definition Tool name 'daylite_get_appointment' and description 'Rufe einen einzelnen Daylite-Termin per ID ab' (Retrieve a single Daylite appointment by ID) indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Rufe einen einzelnen Daylite-Termin per ID ab. It is categorised as a Read tool in the Daylite Claude Connector MCP Server, which means it retrieves data without modifying state.
Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_get_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_get_appointment 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 daylite_get_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_get_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_get_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 →