delete_application_scheduled_task

Delete a scheduled task from an application.

SERVERCoolify SOURCEcoolify-mcp-server
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/coolify/delete-application-scheduled-task.md

What delete_application_scheduled_task does on Coolify

AI agents call delete_application_scheduled_task 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.

Why delete_application_scheduled_task is rated Critical

Deleting a scheduled task permanently removes automation configuration that cannot be restored without manual recreation. While not as severe as deleting an entire application or database, this irreversibly removes operational tasks and their execution schedules. This falls squarely in the Destructive category as it cannot be undone through normal means.

From the tool's definition The tool is named 'delete_application_scheduled_task' and described as 'Delete a scheduled task from an application.' The 'delete' action is explicitly destructive and irreversible.

Questions about delete_application_scheduled_task

What does the delete_application_scheduled_task tool do? +

Delete a scheduled task from an application. 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.

How do I enforce a policy on delete_application_scheduled_task? +

Register the Coolify MCP server in PolicyLayer and add a rule for delete_application_scheduled_task: 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.

What risk level is delete_application_scheduled_task? +

delete_application_scheduled_task 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 delete_application_scheduled_task? +

Yes. Add a rate_limit block to the delete_application_scheduled_task 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 delete_application_scheduled_task completely? +

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

delete_application_scheduled_task is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Coolify, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Coolify's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.