AI agents call taskFieldValueDelete to permanently remove resources in Mcp Taskade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of task field data. Even though it targets a field value rather than an entire task, the deletion cannot be undone and constitutes a destructive action. Given that tasks are likely persistent entities in a task management system (Taskade), deletion of field values represents data loss.
From the tool's definition Tool name contains 'Delete' and description explicitly states 'Delete the field value of a task'. This is an irreversible operation that removes data.
Documented attack patterns abuse exactly the kind of access taskFieldValueDelete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for taskFieldValueDelete:
{
"version": "1",
"default": "deny",
"hide": [
"taskFieldValueDelete"
]
}taskFieldValueDelete 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 the field value of a task. It is categorised as a Destructive tool in the Mcp Taskade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Taskade MCP server in PolicyLayer and add a rule for taskFieldValueDelete: 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 Taskade. Nothing to install.
taskFieldValueDelete 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 taskFieldValueDelete 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 taskFieldValueDelete. 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.
taskFieldValueDelete is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.