scan_test_cleanup
Read-only deep-clean of the project
This record as markdown: /tools/ai-featureboard-featureboard/scan-test-cleanup.md
What scan_test_cleanup does on FeatureBoard
AI agents call scan_test_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.
Why scan_test_cleanup is rated Low
The 'Read-only' designation is the primary signal that this tool retrieves or queries data about the project's test cleanup status without side effects. While 'deep-clean' might suggest destructive operations, the explicit 'read-only' qualifier overrides this and clearly positions it as a data retrieval operation. No data is modified or deleted. Confidence is slightly reduced (0.85 vs.
From the tool's definition Tool name contains 'scan' and description explicitly states 'Read-only deep-clean of the project', indicating it performs inspection without modifying state.
Attacks that exploit this kind of access
The rule that runs scan_test_cleanup 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 scan_test_cleanup, this is the rule to start with:
scan_test_cleanup is read-only, so it stays allowed. 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 scan_test_cleanup call is checked against it from then on.
Questions about scan_test_cleanup
Read-only deep-clean of the project. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for scan_test_cleanup: 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.
scan_test_cleanup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_test_cleanup 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 scan_test_cleanup. 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.
scan_test_cleanup 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