// SCAN REPORT

Testrail

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

11 can modify or destroy data

20 read-only

31 tools total

Community server · catalogue entry verified 30/06/2026

How to control Testrail ↓

TOOL MAP

What Testrail exposes to your agents

Read (20) Write / Execute (10) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Testrail tools

Destructive · High close_run Although 'close_run' does not delete data in the traditional sense, it irreversibly transitions a test run to a terminal state (archived/completed), preventing further modifications and effectively removing it from activ Execute · Medium prepare_run_summary prepare_run_summary Write · Medium add_bulk_results This tool creates or modifies test results in TestRail by posting bulk result data. Write · Medium add_result This tool creates or modifies test result data in TestRail (a test management system).

11 of Testrail'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 Testrail

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

Deny destructive operations

{
  "close_run": {
    "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

{
  "add_bulk_results": {
    "limits": [
      {
        "counter": "add_bulk_results_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "dedupe_against_section": {
    "limits": [
      {
        "counter": "dedupe_against_section_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 Testrail — 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 TESTRAIL →

Instant setup, no code required.

FULL CATALOGUE

All 31 Testrail tools

DESTRUCTIVE 1 tools

Destructive close_run Mark a test run as completed/archived. This is irreversible in TestRail.

EXECUTE 1 tools

Execute prepare_run_summary prepare_run_summary

WRITE 9 tools

Write add_bulk_results Post many results in one TestRail call (much faster than looping add_result). Write add_result add_result Write add_test_cases_bulk add_test_cases_bulk Write create_run Create a new test run. Write create_suite Create a new TestRail suite in a project (only works on multi-suite projects). Write create_test_case Create a single test case in a TestRail section. Write get_or_create_section Resolve a section hierarchy like Auth > Login > Edge Cases, Write update_case Patch an existing test case. fields is forwarded to TestRail as-is. Write update_run Patch an existing test run's metadata. Pass only fields you want to change.

READ 20 tools

Read dedupe_against_section dedupe_against_section Read find_populated_section Find a section that has at least min_cases real cases — useful as a Read flaky_test_detector Pull this case's result across the last N runs and flag flakiness. Read get_results_for_run All result entries for a run — includes comments, defects, who tested when. Read get_run Fetch the full metadata of a single test run. Read get_test_case Fetch a single test case by its TestRail ID. Read get_tests_in_run Tests in a run with their current status (current = latest result). Read list_projects List all TestRail projects visible to the configured user. Read list_runs List test runs in a project. Read list_sections List sections in a suite, returning {id, name, parent_id}. Read list_suites List suites under a TestRail project. Read prepare_cases_from_confluence Fetch a Confluence page + house-style anchors. Returns the context the Read prepare_cases_from_jira Fetch a Jira ticket + house-style anchors. Returns the context the calling Read prepare_cases_from_text prepare_cases_from_text Read prepare_coverage_gaps Return the spec and the existing case titles, plus instructions for the Read prepare_feature_bootstrap prepare_feature_bootstrap Read prepare_lint Return the case batch alongside lint instructions for the calling Claude to evaluate. Read prepare_runs_diff Compute the regression / fix / coverage delta between two runs and return Read preview_house_style Return up to N existing cases from the target section in style-example format. Read search_test_cases List test cases in a project, optionally filtered by suite, section, or title substring.

EXPLORE

Related servers

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

FAQ

Questions about Testrail

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

Yes. The Testrail server exposes 1 destructive tools including close_run. 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 Testrail? +

The Testrail server has 9 write tools including add_bulk_results, add_result, add_test_cases_bulk. 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 Testrail.

How many tools does the Testrail MCP server expose? +

31 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Testrail? +

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

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

ENFORCE POLICY ON TESTRAIL →

Instant setup, no code required.

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