repo_clone · Kubesearch MCP: Risk & Policy

WHAT IT DOES

What repo_clone does on Kubesearch

AI agents invoke repo_clone to trigger actions in Kubesearch. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why repo_clone needs a policy

Cloning a repository involves executing a git operation that fetches remote content and writes it to the local filesystem. This is more than a read (it has side effects) but less than destructive. It falls under Execute because it triggers an external operation (network fetch + filesystem mutation) whose scope depends on the repository argument provided.

From the tool's definition Temporarily clone a public Git repository — clones an external repo to local filesystem, triggering an external network operation and file system write

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repo_clone Rate-limited

repo_clone stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "repo_clone": {
      "limits": [
        {
          "counter": "repo_clone_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kubesearch, so you can run agents against it safely.

FAQ

Questions about repo_clone

What does the repo_clone tool do? +

Temporarily clone a public Git repository so you can review its actual files. Accepts an indexed home-ops repo. It is categorised as a Execute tool in the Kubesearch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on repo_clone? +

Register the Kubesearch MCP server in PolicyLayer and add a rule for repo_clone: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kubesearch. Nothing to install.

What risk level is repo_clone? +

repo_clone is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit repo_clone? +

Yes. Add a rate_limit block to the repo_clone rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block repo_clone completely? +

Set action: deny in the PolicyLayer policy for repo_clone. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides repo_clone? +

repo_clone is provided by the Kubesearch MCP server (perfectra1n/kubesearch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.