All active (and optionally paused) cron jobs for this user.
AI agents call list_cron_jobs 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 retrieves information about scheduled cron jobs without triggering, modifying, or deleting any of them. It is a read-only operation that has no side effects beyond returning existing data. Severity is low because unauthorized access to cron job metadata poses minimal direct risk—the actual execution happens elsewhere and the tool itself cannot be weaponized to trigger jobs or cause damage.
From the tool's definition Tool name 'list_cron_jobs' and description 'All active (and optionally paused) cron jobs for this user' indicate a query/retrieval operation with no modification or execution of jobs themselves.
Attacks that exploit this kind of access
All active (and optionally paused) cron jobs for this user. 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 list_cron_jobs: 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.
list_cron_jobs 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 list_cron_jobs 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 list_cron_jobs. 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.
list_cron_jobs 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 →