List recurring events in the next N days.
AI agents call find_recurring_meetings 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 and returns calendar data about recurring meetings without creating, modifying, deleting, or executing any actions. It is a straightforward read operation on calendar metadata. The blast radius if misused by an agent is minimal—worst case, the agent gains visibility into calendar information, which is low-impact compared to write/execute/destructive operations.
From the tool's definition Tool name 'find_recurring_meetings' and description 'List recurring events in the next N days' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List recurring events in the next N days. 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 find_recurring_meetings: 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.
find_recurring_meetings 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 find_recurring_meetings 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 find_recurring_meetings. 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.
find_recurring_meetings 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 →