import_junit_results · Xray MCP: Risk & Policy

WHAT IT DOES

What import_junit_results does on Xray MCP

AI agents use import_junit_results to create or update resources in Xray MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xray MCP environment.

WHY IT NEEDS A POLICY

Why import_junit_results needs a policy

The tool performs reversible creation and modification operations: it creates test execution records and updates test status data in the Xray system. These are write operations that can be undone (executions can be deleted, statuses can be changed). While it does modify test data, the impact is limited to test management metadata rather than destructive deletion or financial transactions.

From the tool's definition Tool description states it "Automatically creates test execution and updates test statuses" - this modifies data in Xray/Jira by creating new records (test execution) and changing existing data (test statuses).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_junit_results Rate-limited

import_junit_results stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_junit_results": {
      "limits": [
        {
          "counter": "import_junit_results_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xray MCP, so you can run agents against it safely.

FAQ

Questions about import_junit_results

What does the import_junit_results tool do? +

Import JUnit XML test results to Xray. Automatically creates test execution and updates test statuses. It is categorised as a Write tool in the Xray MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_junit_results? +

Register the Xray MCP server in PolicyLayer and add a rule for import_junit_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. Nothing to install.

What risk level is import_junit_results? +

import_junit_results is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_junit_results? +

Yes. Add a rate_limit block to the import_junit_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.

How do I block import_junit_results completely? +

Set action: deny in the PolicyLayer policy for import_junit_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.

What MCP server provides import_junit_results? +

import_junit_results 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.