Find next occurrence of a recurring event
AI agents call next_occurrence 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 retrieves or queries temporal information about recurring events without creating, modifying, executing code, or deleting anything. It fits the Read category definition: 'retrieves or queries data; no side effects.' The blast radius of misuse is minimal—an AI agent could only return incorrect time information, not cause material harm. Severity is low due to the informational nature of the operation.
From the tool's definition Tool name 'next_occurrence' and description 'Find next occurrence of a recurring event' indicate a query operation that retrieves information about when a recurring event will next occur. This is a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Find next occurrence of a recurring 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 next_occurrence: 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.
next_occurrence 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 next_occurrence 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 next_occurrence. 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.
next_occurrence 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 →