toggl_update_time_entry · Tempus MCP: Risk & Policy

WHAT IT DOES

What toggl_update_time_entry does on Tempus MCP

AI agents use toggl_update_time_entry to create or update resources in Tempus MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempus MCP environment.

WHY IT NEEDS A POLICY

Why toggl_update_time_entry needs a policy

This tool modifies existing time entry records reversibly—descriptions, project assignments, and timestamps can all be changed but are not permanently deleted or irreversibly destroyed. The update operation is characteristic of Write category.

From the tool's definition Tool name 'toggl_update_time_entry' and description 'Update an existing time entry. You can modify the description, project assignment, start/stop times, etc.' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggl_update_time_entry Rate-limited

toggl_update_time_entry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "toggl_update_time_entry": {
      "limits": [
        {
          "counter": "toggl_update_time_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tempus MCP, so you can run agents against it safely.

FAQ

Questions about toggl_update_time_entry

What does the toggl_update_time_entry tool do? +

Update an existing time entry. You can modify the description, project assignment, start/stop times, etc. It is categorised as a Write tool in the Tempus MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on toggl_update_time_entry? +

Register the Tempus MCP server in PolicyLayer and add a rule for toggl_update_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 Tempus MCP. Nothing to install.

What risk level is toggl_update_time_entry? +

toggl_update_time_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit toggl_update_time_entry? +

Yes. Add a rate_limit block to the toggl_update_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.

How do I block toggl_update_time_entry completely? +

Set action: deny in the PolicyLayer policy for toggl_update_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.

What MCP server provides toggl_update_time_entry? +

toggl_update_time_entry 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.