add_test_cases_to_run · Zephyr Scale MCP Server MCP

WHAT IT DOES

What add_test_cases_to_run does on Zephyr Scale MCP Server

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

WHY IT NEEDS A POLICY

Why add_test_cases_to_run needs a policy

This tool performs a write operation on test run data—specifically adding test cases to an existing run. It modifies state reversibly (test cases can be removed later), so it falls under Write rather than Execute or Destructive.

From the tool's definition The tool description states 'Add test cases to an existing test run', which modifies an existing test run object by appending test cases to it. This is a create/modify operation that is reversible (test cases can be removed from the run).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_test_cases_to_run Rate-limited

add_test_cases_to_run 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_test_cases_to_run": {
      "limits": [
        {
          "counter": "add_test_cases_to_run_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 Zephyr Scale MCP Server, so you can run agents against it safely.

FAQ

Questions about add_test_cases_to_run

What does the add_test_cases_to_run tool do? +

Add test cases to an existing test run (Cloud only — not supported on Data Center). It is categorised as a Write tool in the Zephyr Scale 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 add_test_cases_to_run? +

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

What risk level is add_test_cases_to_run? +

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

Can I rate-limit add_test_cases_to_run? +

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

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

add_test_cases_to_run is provided by the Zephyr Scale MCP Server MCP server (milo0821/zephyr_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.