List time entries with optional date filtering. Supports querying entries by date range.
AI agents call toggl_list_time_entries to retrieve information from Tempus MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries time entry data with optional filtering by date range. It has no side effects—it does not create, modify, or delete data. It is a straightforward Read operation with minimal security risk when misused by an AI agent, as it only exposes existing data visibility.
From the tool's definition Tool name 'toggl_list_time_entries' and description 'List time entries with optional date filtering. Supports querying entries by date range' indicate retrieval without modification.
Attacks that exploit this kind of access
List time entries with optional date filtering. Supports querying entries by date range. It is categorised as a Read tool in the Tempus MCP MCP Server, which means it retrieves data without modifying state.
Register the Tempus MCP server in PolicyLayer and add a rule for toggl_list_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 Tempus MCP. Nothing to install.
toggl_list_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_list_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_list_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_list_time_entries is provided by the Tempus MCP server (kos-m/tempus-mcp). 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 →