remove_project_custom_field
AI agents call remove_project_custom_field to permanently remove resources in Clockify Time Tracking — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the description is empty (lowering confidence slightly), the tool name strongly suggests removal of a custom field definition from a project. This is a destructive operation that deletes configuration data and cannot be easily undone. Custom fields that are removed may result in loss of associated data structure.
From the tool's definition Tool name 'remove_project_custom_field' indicates deletion or removal of a custom field configuration from a project. The 'remove' verb combined with 'custom_field' suggests irreversible deletion of metadata.
Attacks that exploit this kind of access
remove_project_custom_field. It is categorised as a Destructive tool in the Clockify Time Tracking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for remove_project_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.
remove_project_custom_field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_project_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 remove_project_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.
remove_project_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 →