update_test_run · Xray MCP: Risk & Policy

WHAT IT DOES

What update_test_run does on Xray MCP

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

The tool updates test run results, which is a Write operation that modifies data in the Xray test management system. It is reversible (results can be updated again) and does not delete data or execute arbitrary code, so it does not qualify as Destructive or Execute.

From the tool's definition Tool description states 'Update the result of a test run' — this modifies existing data (test run results) within a test execution, reversibly changing test execution records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_test_run Rate-limited

update_test_run 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": {
    "update_test_run": {
      "limits": [
        {
          "counter": "update_test_run_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 update_test_run

What does the update_test_run tool do? +

Update the result of a test run within a test execution. 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 update_test_run? +

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

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

Can I rate-limit update_test_run? +

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

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

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