AI agents call datetime_business_days to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | Yes | |
start | string | Yes |
Parameters from the server's own tool schema.
This is a read-only utility function that retrieves (calculates) temporal data without altering state or triggering external actions. Even if misused by an agent, the worst outcome is incorrect scheduling advice—low blast radius.
From the tool's definition Tool computes and returns business days between two dates—a pure calculation with no side effects. No creation, modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get business days between two dates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datetime_business_days accepts 2 parameters: end, start. Required: end, start. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for datetime_business_days: 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 UnClick. Nothing to install.
datetime_business_days is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datetime_business_days 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 datetime_business_days. 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.
datetime_business_days is provided by the UnClick MCP server (@unclick/mcp-server). 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 →