Shabbat candle-lighting + havdalah for the given location and date (defaults to today).
AI agents call shabbos_times 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 religious observance times. It does not modify, delete, execute code, move money, or trigger external operations. It purely retrieves and presents calendar/time information, which is a Read operation. The blast radius of misuse is minimal—an agent might request times for wrong locations or dates, but this causes no irreversible harm.
From the tool's definition Tool retrieves Shabbat candle-lighting and havdalah times for a location and date. The verb 'defaults to today' and the informational nature (providing religious calendar times) indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Shabbat candle-lighting + havdalah for the given location and date (defaults to today). 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 shabbos_times: 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.
shabbos_times 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 shabbos_times 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 shabbos_times. 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.
shabbos_times 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 →