Calculate business days between dates
AI agents call get_business_days to retrieve information from MCP Time Server Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a stateless computation that reads date inputs and returns a calculated result. There are no side effects, no data persistence changes, no code execution, and no destructive operations. This is a classic Read category tool—it queries/calculates information without altering system state or triggering external actions.
From the tool's definition Tool name is 'get_business_days' with description 'Calculate business days between dates'. This is a pure calculation/query operation that retrieves or computes information (the count of business days) based on input dates, with no modification, creation,…
Attacks that exploit this kind of access
Calculate business days between dates. It is categorised as a Read tool in the MCP Time Server Node MCP Server, which means it retrieves data without modifying state.
Register the MCP Time Server Node MCP server in PolicyLayer and add a rule for get_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 MCP Time Server Node. Nothing to install.
get_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 get_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 get_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.
get_business_days is provided by the MCP Time Server Node MCP server (pshempel/mcp-time-server-node). 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 →