Query and filter test executions in Xray
AI agents call query_test_executions to retrieve information from Xray MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval operations ('query' and 'filter') on test executions. It does not create, modify, delete, or execute any operations—it only reads and returns information. The blast radius of misuse is minimal, as an AI agent could at worst retrieve test data it shouldn't have access to, but cannot alter or destroy anything.
From the tool's definition Tool name 'query_test_executions' and description 'Query and filter test executions in Xray' indicate retrieval and filtering of existing test execution data without modification or side effects.
Attacks that exploit this kind of access
Query and filter test executions in Xray. It is categorised as a Read tool in the Xray MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Xray MCP Server MCP server in PolicyLayer and add a rule for query_test_executions: 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 Server. Nothing to install.
query_test_executions 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_test_executions 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_test_executions. 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_test_executions is provided by the Xray MCP Server MCP server (jithinjosejacob/xray-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 →