List recent regression runs
AI agents call list_regression_runs to retrieve information from Regression-JIRA Integration System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about past regression test runs. It is a read-only query operation with no side effects, no code execution, no data modification or deletion, and no financial impact. The blast radius of misuse is minimal—an agent could retrieve historical test data but cannot alter it or trigger new operations.
From the tool's definition Tool name 'list_regression_runs' and description 'List recent regression runs' indicate a retrieval operation that queries historical regression test execution data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
List recent regression runs. It is categorised as a Read tool in the Regression-JIRA Integration System MCP Server, which means it retrieves data without modifying state.
Register the Regression-JIRA Integration System MCP server in PolicyLayer and add a rule for list_regression_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 Regression-JIRA Integration System. Nothing to install.
list_regression_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 list_regression_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 list_regression_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.
list_regression_runs is provided by the Regression-JIRA Integration System MCP server (nanyang12138/regression-jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →