update_time_registration · Timelog MCP: Risk & Policy

WHAT IT DOES

What update_time_registration does on Timelog

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

WHY IT NEEDS A POLICY

Why update_time_registration needs a policy

An AI agent can call update_time_registration faster than any human can review — one bad instruction and it creates or modifies resources in Timelog by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_time_registration Rate-limited

update_time_registration 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": {
    "update_time_registration": {
      "limits": [
        {
          "counter": "update_time_registration_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 Timelog, so you can run agents against it safely.

FAQ

Questions about update_time_registration

What does the update_time_registration tool do? +

Update an existing time registration (hours, comment, date, billable status). It is categorised as a Write tool in the Timelog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_time_registration? +

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

What risk level is update_time_registration? +

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

Can I rate-limit update_time_registration? +

Yes. Add a rate_limit block to the update_time_registration 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 update_time_registration completely? +

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

update_time_registration is provided by the Timelog MCP server (timelog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.