AI agents invoke jules_approve_plan to trigger actions in Google Jules MCP. 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.
Approving an execution plan triggers Jules to carry out AI-powered development actions (code changes, automated workflows) on a task. This initiates external operations whose effects depend on the plan contents, making it Execute category. The blast radius is high because an AI agent misusing this could cause unintended code modifications or automated actions across a codebase.
From the tool's definition Approve Jules execution plan for a task
Documented attack patterns abuse exactly the kind of access jules_approve_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Jules MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for jules_approve_plan:
{
"version": "1",
"default": "deny",
"tools": {
"jules_approve_plan": {
"limits": [
{
"counter": "jules_approve_plan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} jules_approve_plan 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.
Free to start. No card required.
Approve Jules execution plan for a task. It is categorised as a Execute tool in the Google Jules MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Google Jules MCP server in PolicyLayer and add a rule for jules_approve_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 Google Jules MCP. Nothing to install.
jules_approve_plan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jules_approve_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_approve_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_approve_plan is provided by the Google Jules MCP server (samihalawa/google-jules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Jules MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Google Jules MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.