AI agents call list_research_sessions to retrieve information from Gemini Research MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing or querying existing research sessions is a read-only operation that retrieves data without side effects. No data is created, modified, deleted, or executed. The empty description slightly reduces confidence, but the clear semantic meaning of 'list_*' operations in API design conventions strongly indicates this is a Read category tool with low severity.
From the tool's definition Tool name 'list_research_sessions' clearly indicates a listing/querying operation with no modification capability. Empty description means we infer function from name alone, which consistently points to retrieval of session data.
Documented attack patterns abuse exactly the kind of access list_research_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gemini Research MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_research_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_research_sessions": {}
}
}list_research_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_research_sessions. It is categorised as a Read tool in the Gemini Research MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gemini Research MCP Server MCP server in PolicyLayer and add a rule for list_research_sessions: 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 Research MCP Server. Nothing to install.
list_research_sessions 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 list_research_sessions 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 list_research_sessions. 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.
list_research_sessions is provided by the Gemini Research MCP Server MCP server (machinemates-ai/gemini-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gemini Research MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Gemini Research MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.