Hebrew date + parsha + holidays for the given (YYYY-MM-DD) or today's date.
AI agents call hebcal 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 calendar lookup operation returning Hebrew calendar information and holiday data. It has no side effects—it does not modify, delete, or execute any operations. The inputs are date parameters and the output is informational only. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool description states it retrieves 'Hebrew date + parsha + holidays for the given (YYYY-MM-DD) or today's date.' The verbs 'retrieves' and 'queries' indicate data lookup with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Hebrew date + parsha + holidays for the given (YYYY-MM-DD) or today's date. 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 hebcal: 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.
hebcal 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 hebcal 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 hebcal. 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.
hebcal 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 →