This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/toggl-time-entries.md
What toggl_time_entries does on UnClick
AI agents call toggl_time_entries to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
end_date | string | — | |
start_date | string | — |
Parameters from the server's own tool schema.
Why toggl_time_entries is rated Low
This tool queries time-tracking data from Toggl and returns results. There are no side effects, no data modification, no code execution, and no financial impact. The only risk is potential exposure of work-time or billing information, which is low-impact information disclosure.
From the tool's definition Tool name 'toggl_time_entries' and description 'Get Toggl time entries' indicate a retrieval operation. The verb 'Get' explicitly denotes data fetching without modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs toggl_time_entries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For toggl_time_entries, this is the rule to start with:
toggl_time_entries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every toggl_time_entries call is checked against it from then on.
Questions about toggl_time_entries
Get Toggl time entries. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
toggl_time_entries accepts 3 parameters: api_key, end_date, start_date. 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_time_entries: 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_time_entries 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 toggl_time_entries 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_time_entries. 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_time_entries 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue