Manage scheduled tasks: list/create/update/delete tasks and list_executions for applications & services
AI agents call scheduled_tasks to permanently remove resources in Coolify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly includes 'delete tasks' as one of its operations. Since it spans multiple categories (Read for list, Write for create/update, Destructive for delete), the most severe applicable category is Destructive. Misuse by an AI agent could result in irreversible deletion of scheduled tasks in production infrastructure.
From the tool's definition list/create/update/delete tasks and list_executions for applications & services
Attacks that exploit this kind of access
Manage scheduled tasks: list/create/update/delete tasks and list_executions for applications & services. It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP server in PolicyLayer and add a rule for scheduled_tasks: 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 Coolify. Nothing to install.
scheduled_tasks 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 scheduled_tasks 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 scheduled_tasks. 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.
scheduled_tasks is provided by the Coolify MCP server (jurislm/coolify-mcp). 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 →