generate_webhook_token · Clockify Time Tracking MCP

WHAT IT DOES

What generate_webhook_token does on Clockify Time Tracking

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

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_webhook_token Rate-limited

generate_webhook_token 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": {
    "generate_webhook_token": {
      "limits": [
        {
          "counter": "generate_webhook_token_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 generate_webhook_token

What does the generate_webhook_token tool do? +

generate_webhook_token. 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 generate_webhook_token? +

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

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

Can I rate-limit generate_webhook_token? +

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

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

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