Call Gemini API - Non-stream thinking mode
AI agents invoke call_gemini_non_stream_thinking to trigger actions in Gemini MCP Server. 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 Gemini AI models, executing a request and returning a response. It involves invoking an external service whose effects depend on the arguments passed (e.g., the prompt/content sent). This qualifies as Execute since it runs an external operation with argument-dependent behavior.
From the tool's definition Call Gemini API - Non-stream thinking mode
Attacks that exploit this kind of access
Call Gemini API - Non-stream thinking mode. It is categorised as a Execute tool in the Gemini MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for call_gemini_non_stream_thinking: 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 Gemini MCP Server. Nothing to install.
call_gemini_non_stream_thinking 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 call_gemini_non_stream_thinking 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 call_gemini_non_stream_thinking. 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.
call_gemini_non_stream_thinking is provided by the Gemini MCP Server MCP server (lucky-dersan/gemini-mcp-server). 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 →