AI agents call get_test_execution to retrieve information from Xray MCP 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 existing test execution data from Xray Test Management. It does not create, modify, delete, or execute any operations—it only fetches information about a test execution and its results. This is a standard read operation with no destructive or side-effect capabilities.
From the tool's definition Tool name 'get_test_execution' and description 'Get detailed information about a test execution including test run results' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a test execution including test run results. It is categorised as a Read tool in the Xray MCP MCP Server, which means it retrieves data without modifying state.
Register the Xray 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 Xray MCP. 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 Xray MCP server (korfu/mcp-xray). 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 →