update_test_run · Mxray MCP: Risk & Policy

WHAT IT DOES

What update_test_run does on Mxray

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

WHY IT NEEDS A POLICY

Why update_test_run needs a policy

This tool creates or modifies data reversibly by updating test run status and comments in Xray. It does not execute arbitrary code, delete data irreversibly, or move money. The modification is bounded to test execution metadata (status, comments) and can be undone by subsequent updates.

From the tool's definition Tool description states 'Update the status and comment of a test run' — 'update' indicates modification of existing data. The tool modifies test run records within Xray (Jira Cloud integration), changing status and comments, which are reversible changes.

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 Mxray, so you can run agents against it safely.

FAQ

Questions about update_test_run

What does the update_test_run tool do? +

Update the status and comment of a test run within a test execution (requires Xray credentials). It is categorised as a Write tool in the Mxray 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 Mxray 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 Mxray. 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 Mxray MCP server (mxray-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.