execute_tests · Xray MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_tests does on Xray MCP Server

AI agents invoke execute_tests to trigger actions in Xray MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_tests needs a policy

This tool triggers external test execution operations, which qualifies as Execute category. While execution itself may not be destructive to data, it runs arbitrary test code whose side effects are unknown and depend on arguments. The blast radius is high because misconfigured or malicious tests could impact systems, infrastructure, or produce unintended side effects.

From the tool's definition Tool description states 'Create and execute a test run' - the execute_tests tool actively runs test cases in the Xray test management system, triggering external operations whose effects depend on the test cases specified as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_tests Rate-limited

execute_tests stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_tests": {
      "limits": [
        {
          "counter": "execute_tests_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about execute_tests

What does the execute_tests tool do? +

Create and execute a test run in Xray for specified test cases. It is categorised as a Execute tool in the Xray MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_tests? +

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

What risk level is execute_tests? +

execute_tests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_tests? +

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

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

execute_tests is provided by the Xray MCP Server MCP server (jithinjosejacob/xray-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.