cronjob_run

What cronjob_run does on Nasbridge

AI agents invoke cronjob_run to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why cronjob_run is rated High

This tool executes code/commands by running a cron job outside its normal schedule. While the actual impact depends on what the cron job contains, the tool itself enables arbitrary command execution on the TrueNAS system. This is Execute rather than Destructive because the harm is contingent on the cron job's contents, not inherent to the tool.

From the tool's definition Tool name 'cronjob_run' combined with description 'Run a cron job immediately' indicates execution of scheduled tasks. The action 'Run' triggers external operations whose effects depend on the cron job's configured commands and arguments.

The rule that runs cronjob_run 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_run, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cronjob_run": {
      "limits": [
        {
          "counter": "cronjob_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about cronjob_run