cronjob_delete

Delete a cron job

SERVERTruenas SOURCEspranab/truenas-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/spranab-truenas-mcp/cronjob-delete.md

WHAT IT DOES

What cronjob_delete does on Truenas

AI agents call cronjob_delete to permanently remove resources in Truenas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cronjob_delete is rated Critical

Deleting a cron job permanently removes scheduled automation tasks. This is irreversible—once deleted, the job must be manually recreated. The impact depends on what the cron job does (could affect backups, maintenance tasks, security monitoring, etc.), justifying 'high' severity. Confidence is high due to explicit 'delete' action and destructive nature.

From the tool's definition Tool name: 'cronjob_delete' with description 'Delete a cron job'. The verb 'delete' combined with the destructive action of removing a scheduled cron job indicates an irreversible operation that cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cronjob_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cronjob_delete, this is the rule to start with:

cronjob_delete Hidden

cronjob_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cronjob_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every cronjob_delete call is checked against it from then on.

FAQ

Questions about cronjob_delete

What does the cronjob_delete tool do? +

Delete a cron job. It is categorised as a Destructive tool in the Truenas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cronjob_delete? +

Register the Truenas MCP server in PolicyLayer and add a rule for cronjob_delete: 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 Truenas. Nothing to install.

What risk level is cronjob_delete? +

cronjob_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cronjob_delete? +

Yes. Add a rate_limit block to the cronjob_delete 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.

How do I block cronjob_delete completely? +

Set action: deny in the PolicyLayer policy for cronjob_delete. 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.

What MCP server provides cronjob_delete? +

cronjob_delete is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →