Get summary statistics for a regression run
AI agents call get_regression_summary 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 queries summary statistics from an existing regression run. It performs a read-only operation that returns information without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal since it only exposes aggregate data about test results.
From the tool's definition Tool name 'get_regression_summary' and description 'Get summary statistics for a regression run' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get summary statistics for a regression run. 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 get_regression_summary: 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.
get_regression_summary 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_regression_summary 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_regression_summary. 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_regression_summary 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 →