Set the Gemini model for this session.
AI agents use set_model to create or update resources in NanoBanana MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NanoBanana MCP environment.
This tool modifies session configuration by changing the active Gemini model. It is a reversible write operation (session state change) with low blast radius since it only affects model selection, not data or financial operations.
From the tool's definition Set the Gemini model for this session
Attacks that exploit this kind of access
Set the Gemini model for this session. It is categorised as a Write tool in the NanoBanana MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NanoBanana MCP server in PolicyLayer and add a rule for set_model: 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 MCP. Nothing to install.
set_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_model 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 set_model. 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.
set_model is provided by the NanoBanana MCP server (pistachiomatt/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 →