update_workspace_custom_field · Clockify Time Tracking MCP

WHAT IT DOES

What update_workspace_custom_field does on Clockify Time Tracking

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

The 'update_' prefix and 'workspace_custom_field' context clearly indicate this tool creates or modifies data (Write category) rather than reading, executing code, or deleting irreversibly. The impact is moderate since custom field updates affect workspace configuration but are reversible.

From the tool's definition Tool name 'update_workspace_custom_field' indicates modification of workspace configuration data. The server description establishes this is a Clockify time-tracking tool managing workspaces and related data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workspace_custom_field Rate-limited

update_workspace_custom_field 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_workspace_custom_field": {
      "limits": [
        {
          "counter": "update_workspace_custom_field_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_workspace_custom_field

What does the update_workspace_custom_field tool do? +

update_workspace_custom_field. 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_workspace_custom_field? +

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

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

Can I rate-limit update_workspace_custom_field? +

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

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

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