jules_create_and_wait · Jules MCP Server MCP: Risk & Policy

WHAT IT DOES

What jules_create_and_wait does on Jules MCP Server

AI agents invoke jules_create_and_wait to trigger actions in Jules MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why jules_create_and_wait needs a policy

This tool triggers automated AI coding task execution by creating a session and running it to completion. It initiates external operations (AI-generated code changes, potentially interacting with GitHub repositories) whose effects depend on the arguments provided. This goes beyond a simple write as it executes an AI workflow end-to-end, potentially modifying code and synchronizing with GitHub.

From the tool's definition Creates a Jules session AND waits for it to complete in a single operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jules_create_and_wait Rate-limited

jules_create_and_wait stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jules_create_and_wait": {
      "limits": [
        {
          "counter": "jules_create_and_wait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jules MCP Server, so you can run agents against it safely.

FAQ

Questions about jules_create_and_wait

What does the jules_create_and_wait tool do? +

Creates a Jules session AND waits for it to complete in a single operation. It is categorised as a Execute tool in the Jules MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jules_create_and_wait? +

Register the Jules MCP Server MCP server in PolicyLayer and add a rule for jules_create_and_wait: 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.

What risk level is jules_create_and_wait? +

jules_create_and_wait is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jules_create_and_wait? +

Yes. Add a rate_limit block to the jules_create_and_wait 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.

How do I block jules_create_and_wait completely? +

Set action: deny in the PolicyLayer policy for jules_create_and_wait. 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.

What MCP server provides jules_create_and_wait? +

jules_create_and_wait 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.