Send any query to Gemini-3-pro-preview model
AI agents invoke gemini_query to trigger actions in Claude Code Gemini MCP. 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 dispatches arbitrary queries to an external AI model via an OpenAI-compatible API. While it is primarily a retrieval/generation tool, it constitutes an external execution operation rather than a simple local read, since it invokes a third-party model service with open-ended inputs.
From the tool's definition "Send any query to Gemini-3-pro-preview model" — triggers an external operation (API call to a remote Gemini model) whose effects depend on the query arguments supplied.
Attacks that exploit this kind of access
Send any query to Gemini-3-pro-preview model. It is categorised as a Execute tool in the Claude Code Gemini MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Code Gemini MCP server in PolicyLayer and add a rule for gemini_query: 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 Code Gemini MCP. Nothing to install.
gemini_query 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_query 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_query. 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_query is provided by the Claude Code Gemini MCP server (shunl12324/claude-code-gemini-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →