// SCAN REPORT

Debug Companion MCP

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

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

Last updated: 4 Jul 2026

3 can modify or destroy data

3 read-only

6 tools total

Community server · catalogue entry verified 04/07/2026

How to control Debug Companion MCP ↓

TOOL MAP

What Debug Companion MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Debug Companion MCP tools

Execute · High run_pytest Running pytest executes arbitrary Python test code whose behavior depends on the test suite contents. Execute · High analyze_error_with_gemini The tool likely triggers an external API call to Google Gemini to analyze errors and suggest fixes. Execute · High debug_project The server description indicates it executes pytest and performs code analysis.

3 of Debug Companion MCP'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 Companion MCP

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

Cap read operations

{
  "extract_failures": {
    "limits": [
      {
        "counter": "extract_failures_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 Companion 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 DEBUG COMPANION →

Instant setup, no code required.

FULL CATALOGUE

All 6 Debug Companion MCP tools

EXECUTE 3 tools

Execute analyze_error_with_gemini analyze_error_with_gemini Execute debug_project debug_project Execute run_pytest run_pytest

READ 3 tools

Read extract_failures extract_failures Read open_context open_context Read ping ping

EXPLORE

Related servers

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

FAQ

Questions about Debug Companion MCP

Is the Debug Companion MCP server safe to use without restrictions? +

The Debug Companion MCP 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 Debug Companion MCP server expose? +

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

How do I enforce a policy on Debug Companion MCP? +

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

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

ENFORCE POLICY ON DEBUG COMPANION →

Instant setup, no code required.

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