Deep analysis with Gemini — sends a large context (up to 1M tokens). Use for analyzing entire files, large diffs, or complex codebases. Longer timeout (3 min).
AI agents invoke gemini_analyze 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 triggers an external API call to Google's Gemini service, executing a remote AI inference operation. While it is read-like in intent (analysis/review), it actively dispatches data to an external third-party system, which constitutes triggering an external operation.
From the tool's definition 'sends a large context (up to 1M tokens)' to an external Gemini AI service for 'analyzing entire files, large diffs, or complex codebases'
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access gemini_analyze 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_analyze:
{
"version": "1",
"default": "deny",
"tools": {
"gemini_analyze": {
"limits": [
{
"counter": "gemini_analyze_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}gemini_analyze 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.
Deep analysis with Gemini — sends a large context (up to 1M tokens). Use for analyzing entire files, large diffs, or complex codebases. Longer timeout (3 min). 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_analyze: 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_analyze 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_analyze 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_analyze. 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_analyze 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.