List active conversation IDs for the gemini_chat tool
AI agents call gemini_list_conversations to retrieve information from Gemini MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing conversation identifiers. It performs data retrieval only, with no capability to modify, execute external operations, delete data, or commit financial obligations. The narrow scope (listing conversation IDs) and read-only nature align with the 'Read' category. Severity is low because conversation IDs are typically non-sensitive metadata, and misuse poses minimal risk.
From the tool's definition Tool name 'gemini_list_conversations' and description 'List active conversation IDs' indicate retrieval of conversation metadata without modification or side effects.
Attacks that exploit this kind of access
List active conversation IDs for the gemini_chat tool. It is categorised as a Read tool in the Gemini MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for gemini_list_conversations: 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.
gemini_list_conversations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gemini_list_conversations 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_list_conversations. 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_list_conversations is provided by the Gemini MCP Server MCP server (jeff-emmett/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 →