create_workspace_custom_field
AI agents use create_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.
This tool creates (adds) a new custom field configuration, which is a reversible modification of workspace settings. It does not execute arbitrary code, delete data irreversibly, or move money. Sibling tools like 'create_client' and 'create_assignment' follow the same Write pattern.
From the tool's definition Tool name 'create_workspace_custom_field' indicates creation of a new custom field resource within a workspace.
Attacks that exploit this kind of access
create_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.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for create_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.
create_workspace_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →