Remove crontab entries matching a pattern. Shows what will be removed.
AI agents call remove_cron_entry to permanently remove resources in Mcp Crontab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes scheduling configurations. While it shows what will be removed (preview/confirmation), the action itself is irreversible and constitutes destructive modification of system state. Removing a cron entry stops automated tasks from running, which could disrupt critical services, backups, or maintenance jobs.
From the tool's definition 'Remove crontab entries' - the tool irreversibly deletes cron job configurations. Crontab entries, once removed, cannot be automatically recovered without manual recreation or backups.
Attacks that exploit this kind of access
Remove crontab entries matching a pattern. Shows what will be removed. It is categorised as a Destructive tool in the Mcp Crontab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Crontab MCP server in PolicyLayer and add a rule for remove_cron_entry: 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 Mcp Crontab. Nothing to install.
remove_cron_entry 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 remove_cron_entry 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 remove_cron_entry. 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.
remove_cron_entry is provided by the Mcp Crontab MCP server (jasona7/mcp-crontab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →