// SCAN REPORT

Daylite Claude Connector

29 tools. 14 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

14 can modify or destroy data

15 read-only

29 tools total

Community server · catalogue entry verified 30/06/2026

How to control Daylite Claude Connector ↓

TOOL MAP

What Daylite Claude Connector exposes to your agents

Read (15) Write / Execute (12) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Daylite Claude Connector tools

Destructive · High daylite_delete_appointment Deletion of calendar appointments cannot be undone and constitutes irreversible data loss. Destructive · High daylite_delete_task This tool permanently removes tasks from the CRM system without the ability to undo the action. Write · Medium daylite_create_appointment This tool creates calendar appointments in a CRM system. Write · Medium daylite_create_company This tool creates (writes) a new company record in Daylite CRM.

14 of Daylite Claude Connector's 29 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Daylite Claude Connector

PolicyLayer is an MCP gateway — it sits between your AI agents and Daylite Claude Connector, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "daylite_delete_appointment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "daylite_create_appointment": {
    "limits": [
      {
        "counter": "daylite_create_appointment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "daylite_debug_raw": {
    "limits": [
      {
        "counter": "daylite_debug_raw_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Daylite Claude Connector — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DAYLITE CLAUDE CONNECTOR →

Instant setup, no code required.

FULL CATALOGUE

All 29 Daylite Claude Connector tools

DESTRUCTIVE 2 tools

Destructive daylite_delete_appointment Lösche einen Termin aus Daylite. Destructive daylite_delete_task Lösche einen Task aus Daylite.

WRITE 12 tools

Write daylite_create_appointment Erstelle einen neuen Termin in Daylite. Write daylite_create_company Neue Firma in Daylite anlegen Write daylite_create_contact Neuen Kontakt in Daylite anlegen Write daylite_create_opportunity Neue Verkaufschance in Daylite anlegen Write daylite_create_project Neues Projekt in Daylite anlegen Write daylite_create_task Erstelle einen neuen Task in Daylite. Write daylite_update_appointment Aktualisiere einen bestehenden Daylite-Termin. Write daylite_update_company Bestehende Firma in Daylite aktualisieren Write daylite_update_contact Bestehenden Kontakt in Daylite aktualisieren Write daylite_update_opportunity Bestehende Verkaufschance aktualisieren Write daylite_update_project Bestehendes Projekt aktualisieren Write daylite_update_task Aktualisiere einen bestehenden Daylite-Task.

READ 15 tools

Read daylite_debug_raw Debug: Zeigt die rohe API-Antwort für einen Endpoint (für Troubleshooting) Read daylite_get_appointment Rufe einen einzelnen Daylite-Termin per ID ab. Read daylite_get_company Eine bestimmte Firma aus Daylite abrufen Read daylite_get_contact Einen bestimmten Kontakt aus Daylite abrufen Read daylite_get_opportunity Eine bestimmte Verkaufschance aus Daylite abrufen Read daylite_get_project Ein bestimmtes Projekt aus Daylite abrufen Read daylite_get_task Rufe einen einzelnen Daylite-Task per URL ab. Read daylite_list_appointments Liste Termine aus Daylite auf. Optional filterbar nach Zeitraum. Read daylite_list_companies Firmen aus Daylite auflisten (REST API) Read daylite_list_contacts Kontakte aus Daylite auflisten (REST API) Read daylite_list_opportunities Verkaufschancen (Opportunities) aus Daylite auflisten Read daylite_list_pipelines Verfügbare Pipelines aus Daylite auflisten Read daylite_list_projects Projekte aus Daylite auflisten Read daylite_list_tasks Liste alle Tasks/Aufgaben aus Daylite auf. Read daylite_search Übergreifend in Daylite suchen (Kontakte, Firmen, Opportunities, Projekte)

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Daylite Claude Connector

Can an AI agent delete data through the Daylite Claude Connector MCP server? +

Yes. The Daylite Claude Connector server exposes 2 destructive tools including daylite_delete_appointment, daylite_delete_task. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Daylite Claude Connector? +

The Daylite Claude Connector server has 12 write tools including daylite_create_appointment, daylite_create_company, daylite_create_contact. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Daylite Claude Connector.

How many tools does the Daylite Claude Connector MCP server expose? +

29 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 14 can modify, create, or delete data.

How do I enforce a policy on Daylite Claude Connector? +

Register the Daylite Claude Connector MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Daylite Claude Connector tool call.

Deterministic rules across all 29 Daylite Claude Connector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DAYLITE CLAUDE CONNECTOR →

Instant setup, no code required.

29 Daylite Claude Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.