create_test_execution · Mxray MCP: Risk & Policy

WHAT IT DOES

What create_test_execution does on Mxray

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

This tool creates test executions in Jira Cloud, which is a reversible operation—test executions can be modified or deleted by administrators. While it modifies system state, it does not delete data, move funds, or execute arbitrary code. The optional feature of adding tests requires credentials but remains within the domain of creating/modifying test management data.

From the tool's definition create_test_execution creates a new test execution in Jira, and optionally can add tests to it. The description explicitly states the action is to 'Create a new test execution', which is a write operation that modifies the Jira system by introducing new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_test_execution Rate-limited

create_test_execution 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": {
    "create_test_execution": {
      "limits": [
        {
          "counter": "create_test_execution_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 create_test_execution

What does the create_test_execution tool do? +

Create a new test execution in Jira. Optionally add tests to it (requires Xray credentials for adding tests). 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 create_test_execution? +

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

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

Can I rate-limit create_test_execution? +

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

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

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