dismiss_cleanup_finding
Suppress a scan_board_cleanup finding from future scans WITHOUT deleting anything — for false positives or findings you
This record as markdown: /tools/ai-featureboard-featureboard/dismiss-cleanup-finding.md
What dismiss_cleanup_finding does on FeatureBoard
AI agents use dismiss_cleanup_finding to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why dismiss_cleanup_finding is rated Medium
This tool modifies metadata about scan findings (suppression status) rather than deleting or executing arbitrary code. The explicit 'WITHOUT deleting anything' clause confirms no irreversible destruction occurs. The action is reversible (a suppression can typically be undone), making it a Write rather than Destructive. No code execution, financial impact, or data retrieval characterizes this operation.
From the tool's definition Tool suppresses/dismisses a finding state ('WITHOUT deleting anything'), which modifies the state of a scan result or configuration entry—a reversible write operation typical of suppression/acknowledge workflows.
Attacks that exploit this kind of access
The rule that runs dismiss_cleanup_finding 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 dismiss_cleanup_finding, this is the rule to start with:
dismiss_cleanup_finding stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every dismiss_cleanup_finding call is checked against it from then on.
Questions about dismiss_cleanup_finding
Suppress a scan_board_cleanup finding from future scans WITHOUT deleting anything — for false positives or findings you. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for dismiss_cleanup_finding: 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.
dismiss_cleanup_finding is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dismiss_cleanup_finding 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 dismiss_cleanup_finding. 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.
dismiss_cleanup_finding 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.
This server
Across the catalogue