add_tests_to_test_set · Mxray MCP: Risk & Policy

WHAT IT DOES

What add_tests_to_test_set does on Mxray

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

This tool modifies existing test sets by adding tests to them. While the operation is reversible (tests can be removed from sets), it creates new associations and relationships in the test management system. This qualifies as Write rather than Read (it changes state) or Destructive (the action is reversible).

From the tool's definition Tool description states 'Add tests to an existing test set' which is a create/modify operation on test data within Xray Test Management.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tests_to_test_set Rate-limited

add_tests_to_test_set 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": {
    "add_tests_to_test_set": {
      "limits": [
        {
          "counter": "add_tests_to_test_set_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 add_tests_to_test_set

What does the add_tests_to_test_set tool do? +

Add tests to an existing test set via Xray GraphQL (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 add_tests_to_test_set? +

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

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

Can I rate-limit add_tests_to_test_set? +

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

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

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