AI agents call get_test_execution to retrieve information from Mxray without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves test execution details from Jira Cloud's Xray plugin. It performs a read-only operation that fetches existing data without creating, modifying, deleting, or executing any operations. The word 'Get' in the name and 'Get details of' in the description are standard indicators of Read category tools. No arguments that could cause destructive or unintended side effects are mentioned.
From the tool's definition Tool name 'get_test_execution' and description 'Get details of a test execution, including associated test runs' clearly indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a test execution, including associated test runs if Xray is configured. It is categorised as a Read tool in the Mxray MCP Server, which means it retrieves data without modifying state.
Register the Mxray MCP server in PolicyLayer and add a rule for get_test_execution: 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 Mxray. Nothing to install.
get_test_execution 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_execution 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_execution. 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_execution is provided by the Mxray MCP server (mxray-mcp-server). 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 →