get_test_runs
Read recorded test runs (most-recent first) plus a summary: total runs, latest result, and whether the latest is passing.
This record as markdown: /tools/ai-featureboard-featureboard/get-test-runs.md
What get_test_runs does on FeatureBoard
AI agents call get_test_runs 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 get_test_runs is rated Low
This tool retrieves and queries historical test run data without side effects. It performs a read-only operation that returns test metadata and summaries, fitting the 'Read' category definition of data retrieval with no side effects. The low severity reflects that misuse would only expose or report existing test information, with no capability to modify, delete, or execute operations.
From the tool's definition Tool name is 'get_test_runs' and description states 'Read recorded test runs' with retrieval of summary data (total runs, latest result, passing status). No modification, deletion, or execution of tests—only querying existing test run records.
Attacks that exploit this kind of access
The rule that runs get_test_runs 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 get_test_runs, this is the rule to start with:
get_test_runs 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 get_test_runs call is checked against it from then on.
Questions about get_test_runs
Read recorded test runs (most-recent first) plus a summary: total runs, latest result, and whether the latest is passing. 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 get_test_runs: 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.
get_test_runs 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 get_test_runs 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 get_test_runs. 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.
get_test_runs 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