Chat with Gemini 3.1 Flash model. Supports multi-turn conversations with up to 10 reference images.
AI agents invoke gemini_chat to trigger actions in Nanobanana. 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 AI model inference operation (Gemini 3.1 Flash) with arbitrary user-supplied input, including images. It is not a simple read/query of stored data — it executes a request to an external service whose effects depend on the arguments. Misuse could involve prompt injection, generation of harmful content, or unintended data leakage via image inputs.
From the tool's definition "Chat with Gemini 3.1 Flash model. Supports multi-turn conversations with up to 10 reference images."
Attacks that exploit this kind of access
Chat with Gemini 3.1 Flash model. Supports multi-turn conversations with up to 10 reference images. It is categorised as a Execute tool in the Nanobanana MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nanobanana 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 Nanobanana. 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 Nanobanana MCP server (@ycse/nanobanana-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 →