cleanup_worktree
Remove a ticket
This record as markdown: /tools/ai-featureboard-featureboard/cleanup-worktree.md
What cleanup_worktree does on FeatureBoard
AI agents call cleanup_worktree 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 cleanup_worktree is rated Critical
This tool permanently deletes tickets, which is an irreversible destructive action on project data. Even though the blast radius is limited to individual tickets (not the entire system), the destructive nature and potential loss of work context justifies 'Destructive' categorization and 'high' severity.
From the tool's definition Tool name 'cleanup_worktree' combined with description 'Remove a ticket' indicates irreversible deletion of project work items. The action cannot be undone and eliminates data from the project board.
Attacks that exploit this kind of access
The rule that runs cleanup_worktree 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 cleanup_worktree, this is the rule to start with:
cleanup_worktree 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 cleanup_worktree call is checked against it from then on.
Questions about cleanup_worktree
Remove a ticket. 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 cleanup_worktree: 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.
cleanup_worktree 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 cleanup_worktree 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 cleanup_worktree. 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.
cleanup_worktree 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