// SCAN REPORT

TestRail MCP Server

77 tools. 39 can modify or destroy data without limits.

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

Last updated: 1 Jul 2026

39 can modify or destroy data

38 read-only

77 tools total

Community server · catalogue entry verified 01/07/2026

How to control TestRail MCP Server ↓

TOOL MAP

What TestRail MCP Server exposes to your agents

Read (38) Write / Execute (30) Destructive / Financial (9)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous TestRail MCP Server tools

Destructive · High delete_attachment This tool permanently removes an attachment from TestRail, which cannot be undone. Destructive · High delete_case Deleting a test case permanently removes data that cannot be recovered without backup restoration. Destructive · High delete_cases Deletion of test cases cannot be undone and represents permanent loss of test data and associated metadata. Destructive · High delete_milestone This tool performs an irreversible deletion operation on a milestone object in TestRail.

39 of TestRail MCP Server's 77 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 MCP Server

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

Deny destructive operations

{
  "delete_attachment": {
    "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_attachment_to_case": {
    "limits": [
      {
        "counter": "add_attachment_to_case_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_attachment": {
    "limits": [
      {
        "counter": "get_attachment_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 MCP Server — 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 77 TestRail MCP Server tools

DESTRUCTIVE 9 tools

Destructive delete_attachment Delete an attachment Destructive delete_case Delete a test case Destructive delete_cases Delete multiple test cases Destructive delete_milestone Delete a milestone Destructive delete_plan Delete a test plan Destructive delete_plan_entry Delete a test plan entry Destructive delete_run Delete a test run Destructive delete_run_from_plan_entry Delete a test run from a plan entry Destructive delete_section Delete a section

WRITE 30 tools

Write add_attachment_to_case Add an attachment to a test case Write add_attachment_to_plan Add an attachment to a test plan Write add_attachment_to_plan_entry Add an attachment to a test plan entry Write add_attachment_to_result Add an attachment to a test result Write add_attachment_to_run Add an attachment to a test run Write add_case Create a new test case Write add_milestone Create a new milestone Write add_plan Create a new test plan Write add_plan_entry Add test runs to a test plan Write add_result Add a test result Write add_result_for_case Add a test result for a specific case in a run Write add_results Add multiple test results by test IDs Write add_results_for_cases Add multiple test results for cases in a run Write add_run Create a new test run Write add_run_to_plan_entry Add a test run to an existing plan entry Write add_section Create a new section Write add_suite Create a new test suite Write close_plan Close a test plan Write close_run Close a test run Write copy_cases_to_section Copy test cases to another section Write move_cases_to_section Move test cases to another section Write move_section Move a section to another parent or position Write update_case Update an existing test case Write update_milestone Update an existing milestone Write update_plan Update an existing test plan Write update_plan_entry Update a test plan entry Write update_run Update an existing test run Write update_run_in_plan_entry Update a test run inside a plan entry Write update_section Update an existing section Write update_suite Update an existing test suite

READ 38 tools

Read get_attachment Get/download an attachment by ID Read get_attachments_for_case Get all attachments for a test case Read get_attachments_for_plan Get all attachments for a test plan Read get_attachments_for_plan_entry Get all attachments for a test plan entry Read get_attachments_for_run Get all attachments for a test run Read get_attachments_for_test Get all attachments for a test Read get_case Get a specific test case by ID Read get_case_fields Get all available test case fields Read get_case_statuses Get all available test case statuses (Enterprise) Read get_case_types Get all available test case types Read get_cases Get test cases for a project/suite Read get_configs Get all configurations for a project Read get_current_user Get the current authenticated user Read get_history_for_case Get the edit history for a test case Read get_milestone Get a specific milestone by ID Read get_milestones Get milestones for a project Read get_plan Get a specific test plan by ID Read get_plans Get test plans for a project Read get_priorities Get all available test case priorities Read get_project Get a specific project by ID Read get_projects Get all TestRail projects Read get_result_fields Get all available result custom fields Read get_results Get results for a test Read get_results_for_case Get results for a test case in a run Read get_results_for_run Get results for a test run Read get_run Get a specific test run by ID Read get_runs Get test runs for a project Read get_section Get a specific section by ID Read get_sections Get all sections for a project/suite Read get_statuses Get all available test result statuses Read get_suite Get a specific test suite by ID Read get_suites Get all test suites for a project Read get_templates Get all templates for a project Read get_test Get a specific test by ID Read get_tests Get tests for a test run Read get_user Get a user by ID Read get_user_by_email Get a user by email address Read get_users Get all users (optionally filtered by project)

EXPLORE

Related servers

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

FAQ

Questions about TestRail MCP Server

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

Yes. The TestRail MCP Server server exposes 9 destructive tools including delete_attachment, delete_case, delete_cases. 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 MCP Server? +

The TestRail MCP Server server has 30 write tools including add_attachment_to_case, add_attachment_to_plan, add_attachment_to_plan_entry. 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 MCP Server.

How many tools does the TestRail MCP Server MCP server expose? +

77 tools across 3 categories: Destructive, Read, Write. 38 are read-only. 39 can modify, create, or delete data.

How do I enforce a policy on TestRail MCP Server? +

Register the TestRail MCP Server 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 MCP Server tool call.

Deterministic rules across all 77 TestRail MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TESTRAIL →

Instant setup, no code required.

77 TestRail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.