list_test_variants
List the per-model test variants present for a ticket (test/<ticket>.<model>.test.js) and which model tiers cover it. Reads the project
This record as markdown: /tools/ai-featureboard-featureboard/list-test-variants.md
What list_test_variants does on FeatureBoard
AI agents call list_test_variants 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 list_test_variants is rated Low
This tool retrieves and queries test variant files and their metadata to report on existing test coverage without creating, modifying, deleting, or executing anything. It is purely informational about the project structure. The lowest severity applies since reading test metadata has no blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_test_variants' and description states 'List the per-model test variants' and explicitly says 'Reads the project'. The verb 'list' and action of reading file metadata with no modification capability indicate a read-only operation.
Attacks that exploit this kind of access
The rule that runs list_test_variants 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 list_test_variants, this is the rule to start with:
list_test_variants 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 list_test_variants call is checked against it from then on.
Questions about list_test_variants
List the per-model test variants present for a ticket (test/<ticket>.<model>.test.js) and which model tiers cover it. Reads 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 list_test_variants: 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.
list_test_variants 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 list_test_variants 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 list_test_variants. 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.
list_test_variants 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