reject_time_off_request · Clockify Time Tracking MCP

WHAT IT DOES

What reject_time_off_request does on Clockify Time Tracking

AI agents use reject_time_off_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 reject_time_off_request needs a policy

Rejecting a time-off request changes the state of that request in the Clockify system. This is a reversible modification (the request can be re-approved or modified later), not destructive deletion. It does not involve financial transactions, code execution, or irreversible data loss.

From the tool's definition Tool name 'reject_time_off_request' indicates modification of time-off request status. Related tools on the server include 'approve_time_off_request' and other state-changing operations (change_invoice_status, bulk_update_time_entries), confirming this is a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_time_off_request Rate-limited

reject_time_off_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": {
    "reject_time_off_request": {
      "limits": [
        {
          "counter": "reject_time_off_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 reject_time_off_request

What does the reject_time_off_request tool do? +

reject_time_off_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 reject_time_off_request? +

Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for reject_time_off_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 reject_time_off_request? +

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

Can I rate-limit reject_time_off_request? +

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

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

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