// SCAN REPORT

Cert Manager

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

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

Last updated: 11 Jun 2026

2 can modify or destroy data

6 read-only

8 tools total

Community server · catalogue entry verified 11/06/2026

How to control Cert Manager ↓

TOOL MAP

What Cert Manager exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Cert Manager tools

Execute · High switch_context Switching the Kubernetes context changes which cluster all subsequent operations target. Execute · High renew_certificate Renewing a certificate forces an active operation against the Kubernetes/cert-manager infrastructure.

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

POLICY

How to control Cert Manager

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

Cap read operations

{
  "get_certificate": {
    "limits": [
      {
        "counter": "get_certificate_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 Cert Manager — 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 CERT MANAGER →

Free to start. No card required.

FULL CATALOGUE

All 8 Cert Manager tools

EXECUTE 2 tools

Execute renew_certificate Forces renewal of a certificate in a given namespace Execute switch_context Switch kubeconfig context

READ 6 tools

Read get_certificate Gets detailed information about certificate. Both namespace_name and resource_name (name of certificate) are r Read get_current_context Get current kubeconfig context Read list_certificates List certificates within provided namespace_name namespace or within all namespaces if all_namespaces=True (de Read list_contexts List all kubeconfig contexts Read list_issuers Lists issuers (or cluster issuers) along with their statuses and configuration. If list_cluster_issuers is tru Read list_namespaces List all namespaces in cluster

FAQ

Questions about Cert Manager

Is the Cert Manager MCP server safe to use without restrictions? +

The Cert Manager server is primarily read-only with 6 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 Cert Manager MCP server expose? +

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

How do I enforce a policy on Cert Manager? +

Register the Cert Manager 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 Cert Manager tool call.

Deterministic rules across all 8 Cert Manager tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CERT MANAGER →

Free to start. No card required.

8 Cert Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.