Calculate business hours between two times
AI agents call calculate_business_hours 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.
This tool performs a calculation or query operation (determining business hours in a time range) without creating, modifying, deleting, or executing external code. It retrieves or computes information based on inputs. Similar to sibling tools like 'get_business_days' and 'calculate_duration', it is a data retrieval/computation function with no side effects.
From the tool's definition Tool name 'calculate_business_hours' and description 'Calculate business hours between two times' indicate a pure computation/query operation with no state modification or external effects.
Attacks that exploit this kind of access
Calculate business hours between two times. 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 calculate_business_hours: 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.
calculate_business_hours 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 calculate_business_hours 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 calculate_business_hours. 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.
calculate_business_hours 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 →