convex_check_crons
Validate cron job definitions in convex/crons.ts. Checks: handler references use internal (not api), no duplicate names, schedule validity, frequency analysis. Returns cron inventory with issues.
This record as markdown: /tools/io-github-homenshum-nodebench/convex-check-crons.md
What convex_check_crons does on Nodebench
AI agents call convex_check_crons to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why convex_check_crons is rated Low
This is a linting/validation tool that inspects and reports on existing cron configuration. It does not create, modify, delete, or execute any crons — it only reads and analyzes the crons.ts file to detect problems. The output is diagnostic information, making this a Read operation with negligible risk.
From the tool's definition The tool performs validation and analysis only: 'Validate cron job definitions', 'Checks: handler references', 'no duplicate names', 'schedule validity', 'frequency analysis'.
Attacks that exploit this kind of access
The rule that runs convex_check_crons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convex_check_crons, this is the rule to start with:
convex_check_crons is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every convex_check_crons call is checked against it from then on.
Questions about convex_check_crons
Validate cron job definitions in convex/crons.ts. Checks: handler references use internal (not api), no duplicate names, schedule validity, frequency analysis. Returns cron inventory with issues. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for convex_check_crons: 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 Nodebench. Nothing to install.
convex_check_crons 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 convex_check_crons 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 convex_check_crons. 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.
convex_check_crons is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue