add_tests_to_test_plan · Mxray MCP: Risk & Policy

WHAT IT DOES

What add_tests_to_test_plan does on Mxray

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

This tool modifies test plan configuration by adding tests, which is a write operation that changes state but is not destructive (tests and plans remain intact). The severity is medium because misuse could corrupt test planning workflows or add inappropriate tests to plans, but the effects are reversible. Confidence is high given the explicit 'Add' verb and clear intent to modify existing test plans via Xray's API.

From the tool's definition Tool name 'add_tests_to_test_plan' and description 'Add tests to an existing test plan' indicate creation/modification of test plan data. The action is reversible—tests can be removed from a plan.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tests_to_test_plan Rate-limited

add_tests_to_test_plan 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_plan": {
      "limits": [
        {
          "counter": "add_tests_to_test_plan_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_plan

What does the add_tests_to_test_plan tool do? +

Add tests to an existing test plan 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_plan? +

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

add_tests_to_test_plan 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_plan? +

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

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

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