Return the next upcoming event within N hours.
AI agents call whats_next to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries calendar or event data and returns information without altering, creating, or deleting any records. It matches the 'Read' category definition of retrieves or queries data with no side effects. Severity is low because misuse (e.g., an agent repeatedly calling it) causes no harm beyond resource consumption.
From the tool's definition Tool description states 'Return the next upcoming event' — a retrieval operation with no modification, deletion, or side effects. The action is purely informational (query/fetch).
Attacks that exploit this kind of access
Return the next upcoming event within N hours. It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core MCP server in PolicyLayer and add a rule for whats_next: 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 Nexus Core. Nothing to install.
whats_next 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 whats_next 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 whats_next. 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.
whats_next is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →