Count of the Omer for the given date if applicable (returns None outside Omer window).
AI agents call omer_count 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 performs a read-only lookup of a religious calendar date calculation (the Omer period in Jewish tradition). It takes a date parameter and returns a count or None—a pure data retrieval with no side effects, no state changes, no financial impact, and no code execution. It is clearly Read category.
From the tool's definition Tool name 'omer_count' and description 'Count of the Omer for the given date if applicable (returns None outside Omer window)' indicate a query/lookup operation that retrieves calendar information without modifying data or triggering external operations.
Attacks that exploit this kind of access
Count of the Omer for the given date if applicable (returns None outside Omer 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 omer_count: 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.
omer_count 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 omer_count 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 omer_count. 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.
omer_count 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 →