# scan_board_cleanup Read-only deep-clean scan: finds likely-duplicate tickets (grouped by title similarity, each group nominating a keeper + removal candidates), stale/placeholder tickets (old Todo items, placeholder titles), open tickets missing a model:/cap: label (FBMCPF-159 intake orchestration guard — nothing should sit in the queue without a sub-model orchestration decision), and priority-scaled SLA breaches (FBMCPF-198: high-priority tickets stuck In Progress with no recent work-log activity → Agent View of the PolicyLayer registry record for `scan_board_cleanup`. HTML page: https://policylayer.com/tools/ai-featureboard-featureboard/scan-board-cleanup ## Facts - Tool: `scan_board_cleanup` - Server: FeatureBoard (`https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin`) — https://policylayer.com/tools/ai-featureboard-featureboard.md - Homepage: https://github.com/valentil/featureboard-mcp - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "scan_board_cleanup", "arguments": {} } } ``` ## Why scan_board_cleanup is rated Low Despite the complex analysis it performs, scan_board_cleanup is fundamentally a read-only diagnostic tool that scans and reports on board state. It identifies candidates for cleanup but does not execute any changes itself. The blast radius of misuse is minimal—an AI agent could receive inaccurate scan results but cannot be tricked into destructive actions by this tool alone. From the tool's own definition: "Tool description explicitly states 'Read-only deep-clean scan' and performs finding/identifying operations: 'finds likely-duplicate tickets', 'finds...stale/placeholder tickets', 'finds...open tickets missing a label'." ## Use case AI agents call scan_board_cleanup to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FeatureBoard: ```json { "version": "1", "default": "deny", "tools": { "scan_board_cleanup": {} } } ``` ## Other tools on FeatureBoard (214) - `cancel_booking` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/cancel-booking.md - `cleanup_worktree` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/cleanup-worktree.md - `delete_task` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/delete-task.md - `prune_board` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/prune-board.md - `remove_annotation` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-annotation.md - `remove_attachment` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-attachment.md - `remove_company_agreement` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-company-agreement.md - `remove_contact` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-contact.md - `remove_media_comment` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-media-comment.md - `remove_page` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-page.md - `remove_product` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-product.md - `remove_share` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-share.md - `remove_test_page` — Destructive — https://policylayer.com/tools/ai-featureboard-featureboard/remove-test-page.md - `commit_feature` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/commit-feature.md - `create_worktree` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/create-worktree.md - `deploy_site` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/deploy-site.md - `drift_remediate` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/drift-remediate.md - `drift_start` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/drift-start.md - `eval_model_matrix` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/eval-model-matrix.md - `graduate_project` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/graduate-project.md - `set_git_config` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/set-git-config.md - `start_checks` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/start-checks.md - `validate_packaging` — Execute — https://policylayer.com/tools/ai-featureboard-featureboard/validate-packaging.md - `activate_license` — Financial — https://policylayer.com/tools/ai-featureboard-featureboard/activate-license.md - `request_commercial_license` — Financial — https://policylayer.com/tools/ai-featureboard-featureboard/request-commercial-license.md - `set_usage_type` — Other — https://policylayer.com/tools/ai-featureboard-featureboard/set-usage-type.md - `auto_configure_analytics` — Read — https://policylayer.com/tools/ai-featureboard-featureboard/auto-configure-analytics.md - `bug_impact_scan` — Read — https://policylayer.com/tools/ai-featureboard-featureboard/bug-impact-scan.md - `check_updates` — Read — https://policylayer.com/tools/ai-featureboard-featureboard/check-updates.md - `churn_reconcile` — Read — https://policylayer.com/tools/ai-featureboard-featureboard/churn-reconcile.md - …and 184 more: https://policylayer.com/tools/ai-featureboard-featureboard.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-featureboard-featureboard · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-featureboard-featureboard