All events for today (UTC day).
AI agents call today_schedule 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.
The tool fetches read-only schedule information for the current UTC day. It queries and returns data without modifying, creating, or deleting anything. Blast radius is minimal as it only exposes calendar event data.
From the tool's definition "All events for today (UTC day)" — retrieves calendar/schedule data with no side effects
Attacks that exploit this kind of access
All events for today (UTC day). 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 today_schedule: 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.
today_schedule 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 today_schedule 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 today_schedule. 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.
today_schedule 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 →