delete_task
Permanently remove a task from its board.
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.
Attacks that exploit this kind of access
The rule that runs delete_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_task, this is the rule to start with:
delete_task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every delete_task call is checked against it from then on.
Questions about delete_task
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.
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.
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 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.
Across the catalogue