AI agents use toggl_create_time_entry to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
stop | string | — | |
start | string | Yes | |
api_key | string | — | |
project_id | number | — | |
description | string | — | |
workspace_id | number | Yes |
Parameters from the server's own tool schema.
Creating a time entry is a reversible write operation—entries can be modified or deleted afterward. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could create false time records affecting billing/payroll accuracy, but the data is recoverable and the blast radius is limited to time tracking records.
From the tool's definition Tool name explicitly states 'create' and description says 'Create a new Toggl time entry.' This is a write operation that creates a new data record in Toggl's time tracking system.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create a new Toggl time entry. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
toggl_create_time_entry accepts 6 parameters: stop, start, api_key, project_id, description, workspace_id. Required: start, workspace_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for toggl_create_time_entry: 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 UnClick. Nothing to install.
toggl_create_time_entry 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 toggl_create_time_entry 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 toggl_create_time_entry. 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.
toggl_create_time_entry is provided by the UnClick MCP server (@unclick/mcp-server). 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 →