Creates a new Jules session to perform an asynchronous coding task.
AI agents use jules_create_session to create or update resources in Jules MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jules MCP Server environment.
This tool creates a new session resource, which is a reversible write operation. It initializes a coding task session but does not by itself execute code, delete data, or move money. Severity is medium because creating sessions could trigger downstream AI coding operations that interact with repositories.
From the tool's definition Creates a new Jules session to perform an asynchronous coding task
Attacks that exploit this kind of access
Creates a new Jules session to perform an asynchronous coding task. It is categorised as a Write tool in the Jules MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jules MCP Server MCP server in PolicyLayer and add a rule for jules_create_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_create_session 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 jules_create_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_create_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_create_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 →