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

delete_task

Permanently remove a task from its board.

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin
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/ai-featureboard-featureboard/delete-task.md

What delete_task does on FeatureBoard

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

Why delete_task is rated Critical

This tool performs an irreversible data destruction operation. A task deletion cannot be undone, making it Destructive rather than merely Write. The severity is high because an AI agent misusing this could permanently lose project planning data. Confidence is high because the description unambiguously states permanent removal.

From the tool's definition "Permanently remove a task from its board" explicitly indicates irreversible deletion of data with no undo capability.

Questions about delete_task

What does the delete_task tool do? +

Permanently remove a task from its board. It is categorised as a Destructive tool in the FeatureBoard 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_task? +

Register the FeatureBoard 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 FeatureBoard. Nothing to install.

What risk level is delete_task? +

delete_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_task? +

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.

How do I block delete_task completely? +

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.

What MCP server provides delete_task? +

delete_task is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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