Query failed tests from PostgreSQL database
AI agents call query_failed_tests 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/queries test failure data from a database without modifying, deleting, or executing operations. It falls under the Read category. Severity is medium rather than low because querying test databases could expose sensitive information about internal system failures, CI/CD details, or potentially credential leakage if logging is verbose.
From the tool's definition Tool name is 'query_failed_tests' and description states it queries data from a PostgreSQL database. The verb 'query' and context of retrieving test failure data indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Query failed tests from PostgreSQL database. 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 query_failed_tests: 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.
query_failed_tests 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 query_failed_tests 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 query_failed_tests. 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.
query_failed_tests 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 →