AI agents call list_test_executions 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 or queries test execution data from a Jira project with no side effects. It is a standard read operation that does not create, modify, delete, or execute any actions. The low severity reflects that listing test executions has minimal blast radius if misused by an AI agent — the worst outcome would be unauthorized viewing of test data.
From the tool's definition Tool name is 'list_test_executions' and description states it 'List test executions' — this is a retrieval operation that queries existing data without modification.
Attacks that exploit this kind of access
List test executions in a Jira project. 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 list_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. Nothing to install.
list_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 list_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 list_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.
list_test_executions 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 →