Return events overlapping the proposed window.
AI agents call check_conflicts 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 reads existing calendar events to detect conflicts. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward information retrieval task, making it a Read category risk with low severity.
From the tool's definition Tool name 'check_conflicts' and description 'Return events overlapping the proposed window' indicate a query operation that retrieves calendar data without modifying or executing any actions.
Attacks that exploit this kind of access
Return events overlapping the proposed window. 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 check_conflicts: 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.
check_conflicts 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 check_conflicts 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 check_conflicts. 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.
check_conflicts 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 →