New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

chaoxing_delete_task_engine_task

Preview or confirm moving a task-engine task to recycle.

SERVERChaoxing Agent SOURCECr-GH0/chaoxing-agent
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/chaoxing-agent/chaoxing-delete-task-engine-task.md

What chaoxing_delete_task_engine_task does on Chaoxing Agent

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

Why chaoxing_delete_task_engine_task is rated Critical

An AI agent that decides to call chaoxing_delete_task_engine_task doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Chaoxing Agent is gone. There is no undo for destructive operations.

Questions about chaoxing_delete_task_engine_task

What does the chaoxing_delete_task_engine_task tool do? +

Preview or confirm moving a task-engine task to recycle. It is categorised as a Destructive tool in the Chaoxing Agent 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 chaoxing_delete_task_engine_task? +

Register the Chaoxing Agent MCP server in PolicyLayer and add a rule for chaoxing_delete_task_engine_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 Chaoxing Agent. Nothing to install.

What risk level is chaoxing_delete_task_engine_task? +

chaoxing_delete_task_engine_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 chaoxing_delete_task_engine_task? +

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

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

chaoxing_delete_task_engine_task is provided by the Chaoxing Agent MCP server (Cr-GH0/chaoxing-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Chaoxing Agent, 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 Chaoxing Agent'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.