// SCAN REPORT

Code Quality

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

1 write tool that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 30/06/2026

How to control Code Quality ↓

TOOL MAP

What Code Quality exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Code Quality tools

Write · Low set_workspace Setting a workspace root is a reversible configuration change that does not delete data or execute arbitrary code.

1 of Code Quality'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 Code Quality

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

Rate limit write operations

{
  "set_workspace": {
    "limits": [
      {
        "counter": "set_workspace_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_all": {
    "limits": [
      {
        "counter": "analyze_all_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 Code Quality — 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 CODE QUALITY →

Instant setup, no code required.

FULL CATALOGUE

All 7 Code Quality tools

WRITE 1 tools

Write set_workspace Set the workspace root so relative paths resolve correctly.

READ 6 tools

Read analyze_all analyze_all Read analyze_complexity Check cyclomatic complexity with McCabe. Read analyze_content Run all checks on raw Python source code (use when you have file contents, not a path). Read analyze_dead_code Find unused code with vulture. Read analyze_style Check PEP8 style with flake8. Read analyze_types Check type annotations with mypy. NOTE: this tool is slow (10-30s) on first run.

FAQ

Questions about Code Quality

How do I prevent bulk modifications through Code Quality? +

The Code Quality server has 1 write tools including set_workspace. 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 Code Quality.

How many tools does the Code Quality MCP server expose? +

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

How do I enforce a policy on Code Quality? +

Register the Code Quality 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 Code Quality tool call.

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

ENFORCE POLICY ON CODE QUALITY →

Instant setup, no code required.

7 Code Quality tools catalogued and risk-classified — across an index of 43,000+ MCP servers.