// SCAN REPORT

Debug Test

6 tools. 2 can modify or destroy data without limits.

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

Last updated: 30 Jun 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 30/06/2026

How to control Debug Test ↓

TOOL MAP

What Debug Test exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Debug Test tools

Execute · Medium sleep_test The tool executes a blocking sleep/wait operation on the server side, which consumes server resources and can intentionally trigger timeout conditions. Write · Medium create-profile This tool creates user profile data, which is a reversible write operation.

2 of Debug Test's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Debug Test

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

Rate limit write operations

{
  "create-profile": {
    "limits": [
      {
        "counter": "create-profile_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "extra_response": {
    "limits": [
      {
        "counter": "extra_response_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 Debug Test — 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 DEBUG TEST →

Instant setup, no code required.

FULL CATALOGUE

All 6 Debug Test tools

EXECUTE 1 tools

Execute sleep_test Sleeps for a specified duration to test timeouts. Use 95+ seconds to trigger timeout.

WRITE 1 tools

Write create-profile Create a simple user profile with required and optional fields

READ 4 tools

Read extra_response Returns an extra response Read get-request-headers Get all headers that were sent with the current request Read huge_return Returns a huge JSON object Read multiply Multiply two numbers

FAQ

Questions about Debug Test

How do I prevent bulk modifications through Debug Test? +

The Debug Test server has 1 write tools including create-profile. 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 Debug Test.

How many tools does the Debug Test MCP server expose? +

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

How do I enforce a policy on Debug Test? +

Register the Debug Test 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 Debug Test tool call.

Deterministic rules across all 6 Debug Test tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEBUG TEST →

Instant setup, no code required.

6 Debug Test tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Debug Test'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 →