// SCAN REPORT

QA Automation MCP Server

4 tools. 3 can modify or destroy data without limits.

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

Last updated: 2 Jul 2026

3 can modify or destroy data

1 read-only

4 tools total

Community server · catalogue entry verified 02/07/2026

How to control QA Automation MCP Server ↓

TOOL MAP

What QA Automation MCP Server exposes to your agents

Read (1) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous QA Automation MCP Server tools

Execute · High run_test This tool executes test code against web applications via Playwright, which can trigger arbitrary browser actions (clicks, form submissions, navigation, etc.) whose effects depend on the test content generated by the LLM Write · Medium write_test This tool creates new test files based on crawl data and user instructions.

3 of QA Automation MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control QA Automation MCP Server

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

Rate limit write operations

{
  "write_test": {
    "limits": [
      {
        "counter": "write_test_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "crawl_page": {
    "limits": [
      {
        "counter": "crawl_page_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 QA Automation 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 QA AUTOMATION →

Instant setup, no code required.

FULL CATALOGUE

All 4 QA Automation MCP Server tools

EXECUTE 1 tools

Execute run_test Run the generated pytest Playwright test. Automatically heals the test if it fails due to a locator error. Alw

WRITE 1 tools

Write write_test Generate a pytest Playwright test based on crawl data and a user instruction. Always call crawl_page first to

READ 1 tools

Read crawl_page Crawl a webpage and extract all interactive elements like inputs, buttons and links with their locators. Alway

OTHER 1 tools

Other add add

EXPLORE

Related servers

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

FAQ

Questions about QA Automation MCP Server

How do I prevent bulk modifications through QA Automation MCP Server? +

The QA Automation MCP Server server has 1 write tools including write_test. 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 QA Automation MCP Server.

How many tools does the QA Automation MCP Server MCP server expose? +

4 tools across 2 categories: Execute, Write. 1 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on QA Automation MCP Server? +

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

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

ENFORCE POLICY ON QA AUTOMATION →

Instant setup, no code required.

4 QA Automation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.