Erstelle einen neuen Task in Daylite.
AI agents use daylite_create_task 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.
This tool creates new task records in Daylite CRM, which is a reversible modification operation. It does not execute arbitrary code, delete data, or move money. The blast radius is medium because an agent could spam tasks or create misleading entries, but the impact is containable and reversible (tasks can be deleted).
From the tool's definition Tool name 'daylite_create_task' and description 'Erstelle einen neuen Task in Daylite' (Create a new task in Daylite) indicate creation of new data. Server description confirms it enables users to 'create...to-dos directly through natural language.'
Attacks that exploit this kind of access
Erstelle einen neuen Task in Daylite. 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.
Register the Daylite Claude Connector MCP server in PolicyLayer and add a rule for daylite_create_task: 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_create_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the daylite_create_task 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_create_task. 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_create_task 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 →