Gets the current status and details of a Jules session.
AI agents call jules_get_session 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.
This tool retrieves session metadata and status information without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—an AI agent querying this tool can only obtain information about an existing session, posing no risk of unintended side effects.
From the tool's definition Tool name 'jules_get_session' and description 'Gets the current status and details of a Jules session' indicate a retrieval operation with no state modification.
Attacks that exploit this kind of access
Gets the current status and details of a Jules session. 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_get_session: 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_get_session 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_get_session 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_get_session. 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_get_session 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 →