delete_goal
Permanently delete a goal and all its tasks and milestones.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-goal.md
What delete_goal does on FlowDot MCP Server
AI agents call delete_goal to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_goal is rated Critical
This tool irreversibly removes data (a goal and all associated tasks and milestones) with no undo capability. It cannot be undone and represents a destructive operation on a potentially important organizational or project planning entity. While not financial in nature, the permanent loss of goals and their dependent tasks/milestones could have significant operational impact, justifying 'high' severity.
From the tool's definition The tool description explicitly states it will 'Permanently delete a goal and all its tasks and milestones.' The word 'Permanently' combined with 'delete' and the cascading deletion of related entities (tasks and milestones) clearly indicates an irreversible…
Attacks that exploit this kind of access
The rule that runs delete_goal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_goal, this is the rule to start with:
delete_goal 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 FlowDot MCP Server, apply this rule, and every delete_goal call is checked against it from then on.
Questions about delete_goal
Permanently delete a goal and all its tasks and milestones. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_goal: 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 FlowDot MCP Server. Nothing to install.
delete_goal 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_goal 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_goal. 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_goal is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue