// SCAN REPORT

Debugg AI MCP

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

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

Last updated: 3 Aug 2026

5 can modify or destroy data

2 read-only

7 tools total

Community server · catalogue entry checked 11/06/2026

How to control Debugg AI MCP ↓

TOOL MAP

What Debugg AI MCP exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Debugg AI MCP tools

Destructive · High delete_test_case Although described as a 'soft-delete' (logically reversible), the tool is explicitly named 'delete' and performs an irreversible removal operation—hiding the test case from default queries and making it inaccessible thro Destructive · High delete_test_suite Although described as a 'soft-delete' (reversible in principle), the tool irreversibly removes a test suite from normal access and operations. Execute · Medium run_test_suite This tool executes test cases whose effects depend on configuration arguments (suiteUuid, project identifier, targetUrl). Write · Low create_test_suite This tool creates new test suite objects in the system.

5 of Debugg AI MCP'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 Debugg AI MCP

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

Deny destructive operations

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

{
  "create_test_suite": {
    "limits": [
      {
        "counter": "create_test_suite_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_test_suite_results": {
    "limits": [
      {
        "counter": "get_test_suite_results_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 Debugg AI MCP — 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 DEBUGG AI →

Instant setup, no code required.

FULL CATALOGUE

All 7 Debugg AI MCP tools

DESTRUCTIVE 2 tools

Destructive delete_test_case Disable (soft-delete) a test case. The test is hidden from default list queries but not permanently removed. R Destructive delete_test_suite Disable (soft-delete) a test suite. The suite and its tests are hidden from default list queries but not perma

EXECUTE 1 tools

Execute run_test_suite Trigger all test cases in a suite to run asynchronously. Accepts suiteUuid directly, or suiteName + project id

WRITE 2 tools

Write create_test_suite Create a named test suite for a project. A test suite is a collection of test cases that can be run together. Write update_test_case Update a test case\

READ 2 tools

Read get_test_suite_results Fetch a test suite with full per-test results. Returns suite-level status (NEVER_RUN, PENDING, RUNNING, COMPLE Read search_test_suites List and search test suites for a project. Returns paginated results with suite status, test counts, pass rate

EXPLORE

Related servers

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

FAQ

Questions about Debugg AI MCP

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

Yes. The Debugg AI MCP server exposes 2 destructive tools including delete_test_case, delete_test_suite. 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 Debugg AI MCP? +

The Debugg AI MCP server has 2 write tools including create_test_suite, update_test_case. 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 Debugg AI MCP.

How many tools does the Debugg AI MCP server expose? +

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

How do I enforce a policy on Debugg AI MCP? +

Register the Debugg AI 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 Debugg AI MCP tool call.

Deterministic rules across all 7 Debugg AI MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEBUGG AI →

Instant setup, no code required.

7 Debugg AI MCP tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Debugg AI's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →