update_approval_request · Clockify Time Tracking MCP

WHAT IT DOES

What update_approval_request does on Clockify Time Tracking

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

WHY IT NEEDS A POLICY

Why update_approval_request needs a policy

The tool modifies approval request state, which is a reversible write operation. While it could potentially affect financial/payroll outcomes indirectly (given the sibling tool add_invoice_payment), the immediate action is data modification, not financial commitment. Severity is medium because misuse could affect time-tracking approvals and payroll accuracy for employees, but the operation itself is reversible.

From the tool's definition Tool name 'update_approval_request' indicates modification of an existing approval request record. The verb 'update' signifies a write operation that changes data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_approval_request Rate-limited

update_approval_request 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_approval_request": {
      "limits": [
        {
          "counter": "update_approval_request_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 Clockify Time Tracking, so you can run agents against it safely.

FAQ

Questions about update_approval_request

What does the update_approval_request tool do? +

update_approval_request. It is categorised as a Write tool in the Clockify Time Tracking 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_approval_request? +

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

What risk level is update_approval_request? +

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

Can I rate-limit update_approval_request? +

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

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

update_approval_request is provided by the Clockify Time Tracking MCP server (pypi:clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.