Lists your Jules sessions with optional pagination.
AI agents call jules_list_sessions to retrieve information from Jules MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns a list of existing Jules sessions. It has no side effects—no code execution, no data modification, no deletion. Pagination is a standard read parameter. This is a straightforward data retrieval operation falling clearly into the Read category with low severity, as the worst outcome of misuse would be exposure of session metadata.
From the tool's definition Tool name contains 'list' and description states 'Lists your Jules sessions with optional pagination.' This is a read-only operation that retrieves session metadata without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Lists your Jules sessions with optional pagination. It is categorised as a Read tool in the Jules MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jules MCP Server MCP server in PolicyLayer and add a rule for jules_list_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 Jules MCP Server. Nothing to install.
jules_list_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 jules_list_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 jules_list_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.
jules_list_sessions is provided by the Jules MCP Server MCP server (streetquant/jules-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 →