// SCAN REPORT

Testmo

45 tools. 19 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

19 can modify or destroy data

26 read-only

45 tools total

Community server · catalogue entry verified 30/06/2026

How to control Testmo ↓

TOOL MAP

What Testmo exposes to your agents

Read (26) Write / Execute (15) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Testmo tools

Destructive · High testmo_batch_delete_cases This tool permanently removes test cases from the Testmo test management system. Destructive · High testmo_delete_case Deletion of test cases is a destructive operation that cannot be undone. Destructive · High testmo_delete_case_attachments This tool permanently removes data (attachments) from test cases without the ability to undo the operation through normal means. Destructive · High testmo_delete_folder The tool permanently removes folders and all nested test cases without the ability to undo the operation.

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

POLICY

How to control Testmo

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

Deny destructive operations

{
  "testmo_batch_delete_cases": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "testmo_append_automation_run": {
    "limits": [
      {
        "counter": "testmo_append_automation_run_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "testmo_find_folder_by_name": {
    "limits": [
      {
        "counter": "testmo_find_folder_by_name_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 Testmo — 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 TESTMO →

Instant setup, no code required.

FULL CATALOGUE

All 45 Testmo tools

DESTRUCTIVE 4 tools

Destructive testmo_batch_delete_cases Delete multiple test cases (max 100 per call). Destructive testmo_delete_case Delete a test case. Destructive testmo_delete_case_attachments Delete one or more attachments from a test case. Destructive testmo_delete_folder Delete a folder from a project. WARNING: This also deletes all test cases in the folder.

WRITE 15 tools

Write testmo_append_automation_run Append test artifacts, fields, or links to an existing automation run. Write testmo_append_automation_run_thread testmo_append_automation_run_thread Write testmo_batch_create_cases testmo_batch_create_cases Write testmo_batch_update_cases testmo_batch_update_cases Write testmo_complete_automation_run Mark an automation run as completed. Write testmo_complete_automation_run_thread Mark an automation run thread as completed. Write testmo_create_automation_run testmo_create_automation_run Write testmo_create_automation_run_thread testmo_create_automation_run_thread Write testmo_create_case testmo_create_case Write testmo_create_cases testmo_create_cases Write testmo_create_folder Create a new folder in a Testmo project. Write testmo_update_case testmo_update_case Write testmo_update_folder testmo_update_folder Write testmo_upload_case_attachment testmo_upload_case_attachment Write testmo_upload_case_attachments testmo_upload_case_attachments

READ 26 tools

Read testmo_find_folder_by_name Find a folder by its name within a project. Read testmo_get_all_cases Get all test cases in a project or folder, handling pagination automatically. Read testmo_get_automation_run Get details of a specific automation run. Read testmo_get_automation_source Get details of a specific automation source. Read testmo_get_case Get full details of a specific test case, including custom fields and Gherkin scenarios. Read testmo_get_cases_recursive testmo_get_cases_recursive Read testmo_get_field_mappings Get the field value mappings for this Testmo instance. Read testmo_get_folder Get details of a specific folder. Read testmo_get_folders_recursive Get a folder and all descendant subfolders as a nested tree in a single call. Read testmo_get_issue_connection Get details of a specific issue connection. Read testmo_get_milestone Get details of a specific milestone by ID. Read testmo_get_project Get details of a specific Testmo project by ID. Read testmo_get_run Get details of a specific test run. Read testmo_get_web_url Generate a web URL for viewing a resource in Testmo. Read testmo_list_automation_runs testmo_list_automation_runs Read testmo_list_automation_sources testmo_list_automation_sources Read testmo_list_case_attachments List all attachments for a test case. Read testmo_list_cases List test cases in a project or folder. Supports pagination. Read testmo_list_folders List all folders in a Testmo project with full paths. Read testmo_list_issue_connections testmo_list_issue_connections Read testmo_list_milestones testmo_list_milestones Read testmo_list_projects List all accessible Testmo projects. Returns project IDs, names, and metadata. Read testmo_list_run_results testmo_list_run_results Read testmo_list_runs testmo_list_runs Read testmo_search_cases testmo_search_cases Read testmo_search_cases_recursive testmo_search_cases_recursive

EXPLORE

Related servers

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

FAQ

Questions about Testmo

Can an AI agent delete data through the Testmo MCP server? +

Yes. The Testmo server exposes 4 destructive tools including testmo_batch_delete_cases, testmo_delete_case, testmo_delete_case_attachments. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Testmo? +

The Testmo server has 15 write tools including testmo_append_automation_run, testmo_append_automation_run_thread, testmo_batch_create_cases. 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 Testmo.

How many tools does the Testmo MCP server expose? +

45 tools across 4 categories: Destructive, Execute, Read, Write. 26 are read-only. 19 can modify, create, or delete data.

How do I enforce a policy on Testmo? +

Register the Testmo 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 Testmo tool call.

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

ENFORCE POLICY ON TESTMO →

Instant setup, no code required.

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