AI agents call delete_task to permanently remove resources in LunaTask MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the empty description, the tool name unambiguously describes a destructive operation (delete). Deletion of task records is irreversible and removes user data without the possibility of undo. This is the most severe category applicable.
From the tool's definition Tool name 'delete_task' indicates irreversible deletion of task data. Confirmed by sibling tools including 'delete_note' and 'delete_person' on the same LunaTask MCP server, establishing a pattern of destructive operations.
Documented attack patterns abuse exactly the kind of access delete_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LunaTask MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_task:
{
"version": "1",
"default": "deny",
"hide": [
"delete_task"
]
}delete_task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_task. It is categorised as a Destructive tool in the LunaTask MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LunaTask MCP Server MCP server in PolicyLayer and add a rule for delete_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 LunaTask MCP Server. Nothing to install.
delete_task 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_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_task is provided by the LunaTask MCP Server MCP server (tensorfreitas/lunatask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LunaTask MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 LunaTask MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.