Waits for Jules to generate a plan for a session.
AI agents call jules_wait_for_plan 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 waits and monitors for a plan to be generated, which is fundamentally a read/query operation checking session state. It does not create, modify, execute, or delete anything — it simply waits until Jules produces a plan and returns it. Similar in nature to get_session_state but blocking until a plan exists.
From the tool's definition 'Waits for Jules to generate a plan for a session' — this is a polling/waiting operation that reads/retrieves the generated plan state
Attacks that exploit this kind of access
Waits for Jules to generate a plan for a 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_wait_for_plan: 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_wait_for_plan 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_wait_for_plan 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_wait_for_plan. 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_wait_for_plan 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 →