test_runs_by_suite
Organize recorded test runs (from log_test_run) by suite: each suite
This record as markdown: /tools/ai-featureboard-featureboard/test-runs-by-suite.md
What test_runs_by_suite does on FeatureBoard
AI agents call test_runs_by_suite 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 test_runs_by_suite is rated Low
This tool retrieves and organizes test run data that has already been recorded. It performs a read-only query operation to group test runs by their suite, with no capability to create, modify, delete, or execute operations. The low severity reflects minimal risk from misuse—organizing test data cannot directly harm systems or data integrity.
From the tool's definition Tool name 'test_runs_by_suite' and description 'Organize recorded test runs...by suite' indicates retrieval and organization of existing test data. The verb 'organize' in this context means categorizing/querying, not modifying.
Attacks that exploit this kind of access
The rule that runs test_runs_by_suite 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 test_runs_by_suite, this is the rule to start with:
test_runs_by_suite 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 test_runs_by_suite call is checked against it from then on.
Questions about test_runs_by_suite
Organize recorded test runs (from log_test_run) by suite: each suite. 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 test_runs_by_suite: 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.
test_runs_by_suite 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 test_runs_by_suite 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 test_runs_by_suite. 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.
test_runs_by_suite 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