associate_tests_to_execution · Xray MCP Server MCP

WHAT IT DOES

What associate_tests_to_execution does on Xray MCP Server

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

WHY IT NEEDS A POLICY

Why associate_tests_to_execution needs a policy

The tool creates or modifies relationships between test cases and executions, changing the state of test execution metadata. This is a reversible write operation (not destructive, as associations can be modified or removed). Severity is medium because misuse could disrupt test tracking and reporting, but lacks the broad blast radius of arbitrary code execution or destructive operations.

From the tool's definition Tool description: 'Add test cases to an existing test execution' — this modifies the association of tests to an execution, which is a reversible data change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

associate_tests_to_execution Rate-limited

associate_tests_to_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": {
    "associate_tests_to_execution": {
      "limits": [
        {
          "counter": "associate_tests_to_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 Xray MCP Server, so you can run agents against it safely.

FAQ

Questions about associate_tests_to_execution

What does the associate_tests_to_execution tool do? +

Add test cases to an existing test execution. It is categorised as a Write tool in the Xray MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on associate_tests_to_execution? +

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

What risk level is associate_tests_to_execution? +

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

Can I rate-limit associate_tests_to_execution? +

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

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

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