Skip to content

Gemini CLI LeakGuard scan_for_leaks

How to: Gemini CLI LeakGuard scan_for_leaks

client:Gemini CLI transport:streamable-http tool:scan_for_leaks

Add LeakGuard to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "leakguard": {
      "httpUrl": "https://api.youraitools.co/leakguard/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something scan_for_leaks does. Gemini CLI lists the server's tools on connect and calls scan_for_leaks itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that LeakGuard's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 22 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.