Get detailed information for a specific test
AI agents call get_test_details 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 or queries test information without modifying, deleting, or executing anything. It is a straightforward read operation against test data in the regression test system. The blast radius of misuse is minimal—an agent could retrieve test details it shouldn't access, but cannot cause data loss or trigger external operations.
From the tool's definition Tool name 'get_test_details' and description 'Get detailed information for a specific test' indicate a retrieval operation with no side effects. The verb 'Get' and context of retrieving test information align with the Read category (query, fetch operations).
Attacks that exploit this kind of access
Get detailed information for a specific test. 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_test_details: 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_test_details 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_details 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_details. 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_details 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 →