// SCAN REPORT

Kubesearch

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

2 can modify or destroy data

8 read-only

10 tools total

Community server · catalogue entry verified 30/06/2026

How to control Kubesearch ↓

TOOL MAP

What Kubesearch exposes to your agents

Read (8) Write / Execute (1) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Kubesearch tools

Destructive · Medium repo_cleanup Although the tool deletes 'temporary' clones (suggesting limited scope and reversibility through re-cloning), the action itself is a permanent deletion that cannot be undone without re-executing repo_clone. Execute · Medium repo_clone Cloning a repository involves executing a git operation that fetches remote content and writes it to the local filesystem.

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

POLICY

How to control Kubesearch

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

Deny destructive operations

{
  "repo_cleanup": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "kubesearch_get_release": {
    "limits": [
      {
        "counter": "kubesearch_get_release_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 Kubesearch — 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 KUBESEARCH →

Instant setup, no code required.

FULL CATALOGUE

All 10 Kubesearch tools

DESTRUCTIVE 1 tools

Destructive repo_cleanup Delete a temporary clone created by

EXECUTE 1 tools

Execute repo_clone Temporarily clone a public Git repository so you can review its actual files. Accepts an indexed home-ops repo

READ 8 tools

Read kubesearch_get_release Get details for one chart by its kubesearch.dev release id (the Read kubesearch_grep_values Full-text grep across the Helm Read kubesearch_search_images Search kubesearch.dev for container image repositories used across public home-ops clusters (substring match o Read kubesearch_search_releases Search kubesearch.dev for Flux HelmReleases / Argo Applications by chart name (substring, case-insensitive). Read kubesearch_status Report the freshness and size of the locally cached kubesearch.dev data: the release tag (date), when it was Read repo_grep Search the text contents of a previously cloned repository (by Read repo_list_files List files in a previously cloned repository (by Read repo_read_file Read a text file from a previously cloned repository (by

EXPLORE

Related servers

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

FAQ

Questions about Kubesearch

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

Yes. The Kubesearch server exposes 1 destructive tools including repo_cleanup. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Kubesearch MCP server expose? +

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

How do I enforce a policy on Kubesearch? +

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

Deterministic rules across all 10 Kubesearch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON KUBESEARCH →

Instant setup, no code required.

10 Kubesearch tools catalogued and risk-classified — across an index of 43,000+ MCP servers.