// SCAN REPORT

Testops

31 tools. 9 can modify or destroy data without limits.

9 write tools that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

9 can modify or destroy data

22 read-only

31 tools total

Community server · catalogue entry verified 01/07/2026

How to control Testops ↓

TOOL MAP

What Testops exposes to your agents

Read (22) Write / Execute (9) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Testops tools

Execute · High launch_stop This tool executes a command to stop an active launch/test run on an external system. Execute · High testplan_run Creating and running a test launch is an Execute action: it initiates automated test operations whose side effects (test runs, resource consumption, external API calls, etc.) depend on the arguments supplied. Write · Medium launch_create The tool creates a new test run/launch in the TestOps system. Write · Medium testcase_create This tool creates new test case records in a test management system.

9 of Testops's 31 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Testops

PolicyLayer is an MCP gateway — it sits between your AI agents and Testops, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "launch_create": {
    "limits": [
      {
        "counter": "launch_create_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "launch_get": {
    "limits": [
      {
        "counter": "launch_get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Testops — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TESTOPS →

Instant setup, no code required.

FULL CATALOGUE

All 31 Testops tools

EXECUTE 2 tools

Execute launch_stop Close/stop a running launch (ends the run on TestOps). Execute testplan_run Create a launch from a test plan. Body requires launchName.

WRITE 7 tools

Write launch_create Create a test run (launch). Body requires name and projectId. Write testcase_create Create a new test case in TestOps. Required: name and projectId. Optional: steps, customFields, tags, precondi Write testcase_set_scenario Replace all steps in a test case scenario Write testcase_update Update test case metadata (name, description, status, tags, etc.). Does NOT change steps or custom fields — us Write testcase_update_custom_fields Update custom field values for a test case Write testcase_update_step Update one scenario step by its step id. Write testplan_sync Sync test plan with its source: refreshes the test case list in the plan to match the current source.

READ 22 tools

Read launch_get Get a launch by ID Read launch_get_statistic Launch run summary: counts by test status and progress (ready). Read launch_list List launches for a project with pagination Read launch_list_test_results Flat paginated test results for a launch (rows: id, name, testCaseId, status, duration, etc.). Read ping Test tool to verify server connectivity Read project_find_by_name Find a project by exact or partial name match Read project_get_by_id Get a project by its ID Read project_get_custom_field_values Get available values for a custom field with pagination. Returns { items, total, page, size } so the model can Read project_get_custom_fields Get custom field definitions for a project with pagination. Returns { items, total, page, size } for chunked f Read project_get_test_case_trees Get test case trees for a project. Use the returned tree IDs with testcase_list_in_tree. Read project_list List all projects with pagination Read testcase_get Get a test case by ID Read testcase_get_custom_fields Get custom field values for a test case Read testcase_get_detail Aggregated card: name, description, tags, custom fields, and step texts as a simple list. Read testcase_get_scenario Normalized scenario JSON (scenarioSteps, step bodies, expected results). Read testcase_get_step Alias for testcase_get_scenario. Read testcase_list_in_tree List test cases under a project tree with pagination. Use parentNodeId to page into a folder. Read testcase_search_by_aql Search test cases using AQL query with pagination Read testplan_get Get a test plan by ID Read testplan_get_stat Test plan statistics: automated/manual counts, durations. Useful before running to estimate effort. Read testplan_get_test_cases Get test cases from a test plan with pagination Read testplan_list List test plans for a project with pagination

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Testops

How do I prevent bulk modifications through Testops? +

The Testops server has 7 write tools including launch_create, testcase_create, testcase_set_scenario. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Testops.

How many tools does the Testops MCP server expose? +

31 tools across 3 categories: Execute, Read, Write. 22 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Testops? +

Register the Testops MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Testops tool call.

Deterministic rules across all 31 Testops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TESTOPS →

Instant setup, no code required.

31 Testops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.