Calculate days until a target date/event
AI agents call days_until 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.
days_until retrieves or computes temporal information without creating, modifying, deleting, or executing any external operations. It is analogous to 'get_current_time' and 'calculate_duration'—foundational time queries. No financial, destructive, or code-execution implications exist. Low severity because misuse (e.g., spamming calls) poses minimal risk to data or systems.
From the tool's definition Tool calculates and returns days until a target date—a pure time computation with no side effects. The description uses 'Calculate,' indicating data retrieval/query, and the server is 'Time Server' offering 'timezone conversions, date arithmetic...' all…
Attacks that exploit this kind of access
Calculate days until a target date/event. 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 days_until: 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.
days_until 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 days_until 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 days_until. 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.
days_until 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 →