Remove a feature flag from the codebase while preserving the desired code path. This tool provides comprehensive step-by-step instructions for safely removing feature flag code. It guides you through: - Finding all flag occurrences using Grep - Identifying different flag usage patterns (if-else, ...
Part of the Unleash server.
Free to start. No card required.
AI agents may call cleanup_flag to permanently remove or destroy resources in Unleash. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call cleanup_flag in a loop, permanently destroying resources in Unleash. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"cleanup_flag"
]
}See the full Unleash policy for all 13 tools.
These attack patterns abuse exactly the kind of access cleanup_flag gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Remove a feature flag from the codebase while preserving the desired code path. This tool provides comprehensive step-by-step instructions for safely removing feature flag code. It guides you through: - Finding all flag occurrences using Grep - Identifying different flag usage patterns (if-else, ternary, guards, etc.) - Removing flag checks while preserving the correct code path - Cleaning up unused imports and dead code - Verifying and testing the changes When to use this tool: - After a feature flag has been rolled out to 100% and is no longer needed - When deprecating an experimental feature (preserve disabled path) - When cleaning up technical debt from old flags - After a kill switch is no longer necessary Preserve Path Options: -. It is categorised as a Destructive tool in the Unleash MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unleash MCP server in PolicyLayer and add a rule for cleanup_flag: 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 Unleash. Nothing to install.
cleanup_flag 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_flag 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_flag. 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_flag is provided by the Unleash MCP server (Unleash/unleash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Unleash tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.