// SCAN REPORT

QA Agent Pro

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

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

Last updated: 4 Jul 2026

4 can modify or destroy data

3 read-only

7 tools total

Community server · catalogue entry verified 04/07/2026

How to control QA Agent Pro ↓

TOOL MAP

What QA Agent Pro exposes to your agents

Read (3) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous QA Agent Pro tools

Execute · Medium navigate Navigation is an Execute-category action because it triggers an external operation (browser request/page load) with side effects that depend entirely on the argument supplied. Execute · High click Clicking elements in a browser can trigger arbitrary side effects: form submissions, purchases, deletions, authentication flows, downloads, or navigation to external sites. Execute · Low set_viewport This tool modifies the browser's viewport configuration, which is an external browser operation that affects subsequent page rendering and interactions. Execute · Medium type This tool executes browser actions by simulating keyboard input into web page elements.

4 of QA Agent Pro's 7 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 Agent Pro

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

Cap read operations

{
  "get_console_logs": {
    "limits": [
      {
        "counter": "get_console_logs_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 Agent Pro — 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 AGENT PRO →

Instant setup, no code required.

FULL CATALOGUE

All 7 QA Agent Pro tools

EXECUTE 4 tools

Execute click Click an element on the page identified by a CSS selector Execute navigate Navigate to a specific URL in the browser Execute set_viewport Set the browser viewport size (e.g., for mobile simulation) Execute type Type text into an input field identified by a CSS selector

READ 3 tools

Read get_console_logs Get all console logs captured during the session Read get_text Get the text content of an element Read screenshot Take a screenshot of the current page

EXPLORE

Related servers

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

FAQ

Questions about QA Agent Pro

Is the QA Agent Pro MCP server safe to use without restrictions? +

The QA Agent Pro server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the QA Agent Pro MCP server expose? +

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

How do I enforce a policy on QA Agent Pro? +

Register the QA Agent Pro 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 Agent Pro tool call.

Deterministic rules across all 7 QA Agent Pro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON QA AGENT PRO →

Instant setup, no code required.

7 QA Agent Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.