This record as markdown: /tools/nasbridge/cronjob-list.md
What cronjob_list does on Nasbridge
AI agents call cronjob_list to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cronjob_list is rated Low
This tool retrieves and displays cron job information without modifying, executing, or deleting any data. It is a passive information-gathering operation with minimal security risk unless the cron job details themselves contain sensitive information. The low severity reflects that viewing scheduled tasks does not directly impact system operations or data integrity.
From the tool's definition Tool name 'cronjob_list' and description 'List all cron jobs' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation that queries existing data.
Attacks that exploit this kind of access
The rule that runs cronjob_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cronjob_list, this is the rule to start with:
cronjob_list 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 Nasbridge, apply this rule, and every cronjob_list call is checked against it from then on.
Questions about cronjob_list
List all cron jobs. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for cronjob_list: 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 Nasbridge. Nothing to install.
cronjob_list 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 cronjob_list 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 cronjob_list. 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.
cronjob_list is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue