AI agents call delete_task_comment to permanently remove resources in Flux MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a comment, which cannot be undone. Deletion of content is irreversible and represents data destruction. While the blast radius is limited to a single comment rather than entire tasks or projects, it still meets the Destructive category criteria. Severity is high rather than critical because the impact is scoped to a single comment rather than bulk data or the entire collaboration space.
From the tool's definition Tool name is 'delete_task_comment' and description states 'Delete a comment from a task'. The verb 'Delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_task_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_task_comment:
{
"version": "1",
"default": "deny",
"hide": [
"delete_task_comment"
]
}delete_task_comment 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 a comment from a task. It is categorised as a Destructive tool in the Flux MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Flux MCP Server MCP server in PolicyLayer and add a rule for delete_task_comment: 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 Flux MCP Server. Nothing to install.
delete_task_comment 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_comment 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_comment. 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_comment is provided by the Flux MCP Server MCP server (sirsjg/flux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Flux MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Flux MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.