Delete a cron job
AI agents call delete_cron_job to permanently remove resources in cPanel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a cron job removes a scheduled task permanently and cannot be undone without manual recreation. This is a destructive operation that irreversibly removes automation logic from the system. While not as critical as deleting databases or domains, it can break production workflows and monitoring.
From the tool's definition Tool name is 'delete_cron_job' with description 'Delete a cron job'. The verb 'delete' indicates irreversible removal of data/configuration.
Attacks that exploit this kind of access
Delete a cron job. It is categorised as a Destructive tool in the cPanel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for delete_cron_job: 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 cPanel MCP Server. Nothing to install.
delete_cron_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_cron_job 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 delete_cron_job. 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.
delete_cron_job is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_cron_job is one line of cPanel MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →