clickup_create_date_custom_field
Create a date custom field with optional time inclusion.
This record as markdown: /tools/chykalophia-clickup-mcp-server-enhanced/clickup-create-date-custom-field.md
What clickup_create_date_custom_field does on ClickUp MCP Server - Enhanced
AI agents use clickup_create_date_custom_field to create or update resources in ClickUp MCP Server - Enhanced, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP Server - Enhanced environment.
Why clickup_create_date_custom_field is rated Medium
This tool creates new metadata/schema elements (custom fields) in a ClickUp workspace. It is reversible (custom fields can be deleted), non-destructive, and has no financial impact. However, it modifies workspace configuration which could affect task tracking and reporting for teams.
From the tool's definition Tool name 'create_date_custom_field' indicates creation of a new custom field artifact in ClickUp. The description states 'Create a date custom field' which is a data-creation operation.
Attacks that exploit this kind of access
The rule that runs clickup_create_date_custom_field safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ClickUp MCP Server - Enhanced, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_create_date_custom_field, this is the rule to start with:
clickup_create_date_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.
The button opens the PolicyLayer dashboard: create your workspace, connect ClickUp MCP Server - Enhanced, apply this rule, and every clickup_create_date_custom_field call is checked against it from then on.
Questions about clickup_create_date_custom_field
Create a date custom field with optional time inclusion. It is categorised as a Write tool in the ClickUp MCP Server - Enhanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP Server - Enhanced MCP server in PolicyLayer and add a rule for clickup_create_date_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 ClickUp MCP Server - Enhanced. Nothing to install.
clickup_create_date_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 clickup_create_date_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 clickup_create_date_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.
clickup_create_date_custom_field is provided by the ClickUp MCP Server - Enhanced MCP server (chykalophia/clickup-mcp-server---enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ClickUp MCP Server - Enhanced, and thousands of servers like it.
This server
Across the catalogue