Gemini CLI LeadShield Contact Form & B2B Solicitation Blocker leadshield_get_blocked_spam_report
How to: Gemini CLI LeadShield Contact Form & B2B Solicitation Blocker leadshield_get_blocked_spam_report
Add LeadShield Contact Form & B2B Solicitation Blocker to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"leadshield": {
"httpUrl": "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something leadshield_get_blocked_spam_report does. Gemini CLI lists the server's tools on connect and calls leadshield_get_blocked_spam_report itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that LeadShield Contact Form & B2B Solicitation Blocker'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 28 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.