Delete a task permanently from a workspace. This action is irreversible.
AI agents call delete_task to permanently remove resources in Fusebase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a task) and cannot be undone, which is the defining characteristic of the Destructive category. The high severity reflects that an AI agent misusing this tool could permanently remove important work items from a workspace, causing data loss. Confidence is high due to explicit language confirming the permanent and irreversible nature of the action.
From the tool's definition "Delete a task permanently from a workspace. This action is irreversible." The tool explicitly states permanent deletion and irreversibility.
Attacks that exploit this kind of access
Delete a task permanently from a workspace. This action is irreversible. It is categorised as a Destructive tool in the Fusebase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fusebase 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 Fusebase 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 Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →