Send a prompt to Gemini via gemini-cli. Free tier: 1000 req/day. Uses Google account auth (no API key). Good for code review, architecture questions, analysis. 1M token context window.
AI agents invoke gemini_chat to trigger actions in Claude Concilium. 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.
This tool executes an external CLI process (gemini-cli) that sends requests to Google's Gemini service using the user's Google account credentials. It triggers external operations via a subprocess, making it Execute category.
From the tool's definition Send a prompt to Gemini via gemini-cli... Uses Google account auth (no API key)
Documented attack patterns abuse exactly the kind of access gemini_chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Concilium, and nothing reaches the server without passing your rules. This is the rule we recommend for gemini_chat:
{
"version": "1",
"default": "deny",
"tools": {
"gemini_chat": {
"limits": [
{
"counter": "gemini_chat_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} gemini_chat 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.
Free to start. No card required.
Send a prompt to Gemini via gemini-cli. Free tier: 1000 req/day. Uses Google account auth (no API key). Good for code review, architecture questions, analysis. 1M token context window. It is categorised as a Execute tool in the Claude Concilium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Concilium MCP server in PolicyLayer and add a rule for gemini_chat: 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 Claude Concilium. Nothing to install.
gemini_chat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gemini_chat 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.
Set action: deny in the PolicyLayer policy for gemini_chat. 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.
gemini_chat is provided by the Claude Concilium MCP server (spyrae/claude-concilium). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Concilium, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Claude Concilium tools catalogued and risk-classified — across an index of 43,000+ MCP servers.