12 tools from the Testdino MCP Server, categorised by risk level.
View the Testdino policy →`create_manual_test_case` Create new manual test cases with steps, preconditions, postconditions, and metadata (priority, severity, type, layer, behavior). `create_manual_test_suite` Create new test suite folders to organize test cases. Supports nested suites by providing parentSuiteId. `debug_testcase` Debug a test case by aggregating historical failure data across multiple executions. Returns failure patterns, error categories, common error messa... `get_manual_test_case` Get detailed information about a specific manual test case including steps, custom fields, preconditions, postconditions, and all metadata. `get_testcase_details` Get detailed information about a specific test case including error messages, stack traces, test steps, console logs, and artifacts. Can identify b... `health` Verify your connection and validate your PAT. Shows account information, available organizations, and projects with access permissions. `list_manual_test_cases` Search and list manual test cases with comprehensive filtering (project, suite, status, priority, severity, type, layer, behavior, automation statu... `list_manual_test_suites` List test suite hierarchy to find suite IDs for organization. Supports filtering by parent suite. `list_testruns` Browse test runs with powerful filters (branch, time interval, author, commit, environment). Supports pagination and batch operations. `update_manual_test_case` Update existing manual test cases (title, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions). `get_run_details` Get comprehensive details about a specific test run including statistics, test suites, test cases, and metadata. Supports batch operations (comma-s... 3/5 `list_testcase` List test cases with comprehensive filtering (by test run, status, browser, error category, branch, environment, commit, author, spec file, tags, r... 3/5 The Testdino MCP server exposes 12 tools across 2 categories: Read, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Testdino server.
Testdino tools are categorised as Read (10), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept