Critical-risk tools in Taskflow

Critical severity Taskflow MCP Server 5 of 50 tools

5 of the 50 tools in Taskflow are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.

Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.

Tools at critical risk

clear_activity_log Destructive 4/5

Delete all activity log entries. Use with caution — this is irreversible.
clear_data Destructive 4/5

Delete ALL tasks, projects, sessions, notifications, and activity logs. Settings are preserved. Use with extreme caution — this is irreversible.
clear_notifications Destructive 4/5

Delete all notifications. Use with caution — this is irreversible.
delete_project Destructive 4/5

Delete a project by ID. Tasks under this project will be unlinked (project_id set to NULL), not deleted.
delete_task Destructive 4/5

Delete a task by ID. Use sparingly — prefer updating status to "done" instead of deleting.

Attacks that target this class

Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.

Critical-risk tools in Taskflow

Tools at critical risk

Attacks that target this class

More on Taskflow

Enforce policy on Taskflow