Import automated test execution results from various formats (JUnit, Cucumber, Xray JSON, Robot Framework, TestNG)
AI agents use import_test_results to create or update resources in Xray MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xray MCP Server environment.
This tool modifies the state of the Xray Test Management system by ingesting and storing test execution results. It is reversible (results can be updated or corrected in subsequent imports or manual edits), making it Write rather than Destructive.
From the tool's definition Tool description states "Import automated test execution results" which creates or modifies test data in the Xray Test Management system.
Attacks that exploit this kind of access
Import automated test execution results from various formats (JUnit, Cucumber, Xray JSON, Robot Framework, TestNG). It is categorised as a Write tool in the Xray MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xray MCP Server MCP server in PolicyLayer and add a rule for import_test_results: 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.
import_test_results is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_test_results 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 import_test_results. 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.
import_test_results 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 →