import_testng_results · Xray MCP: Risk & Policy

WHAT IT DOES

What import_testng_results does on Xray MCP

AI agents use import_testng_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_testng_results needs a policy

This tool creates new test execution records and modifies existing test status data, which are reversible write operations. It does not delete data (not Destructive), does not move money (not Financial), does not execute arbitrary code in environments outside Xray (not Execute), and is not purely informational (not Read).

From the tool's definition Tool description states it 'Automatically creates test execution and updates test statuses' - both write operations that modify data in Xray Test Management. The tool ingests TestNG XML results and persists changes to test execution records and status fields.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_testng_results Rate-limited

import_testng_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_testng_results": {
      "limits": [
        {
          "counter": "import_testng_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_testng_results

What does the import_testng_results tool do? +

Import TestNG 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_testng_results? +

Register the Xray MCP server in PolicyLayer and add a rule for import_testng_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_testng_results? +

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

Can I rate-limit import_testng_results? +

Yes. Add a rate_limit block to the import_testng_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_testng_results completely? +

Set action: deny in the PolicyLayer policy for import_testng_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_testng_results? +

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