Show the actual code diff for files from a Jules session.
AI agents call show_code_diff 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 and displays code diff information from an existing Jules session. It performs no mutations, deletions, or external operations—it only queries and presents information. The word 'show' confirms it is a read-only operation. Even in the context of a code automation system, displaying diffs is a safe informational action with no side effects.
From the tool's definition Tool name 'show_code_diff' and description 'Show the actual code diff for files from a Jules session' indicate a retrieval operation that displays differences between code versions without modifying data.
Attacks that exploit this kind of access
Show the actual code diff for files from 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 show_code_diff: 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.
show_code_diff 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 show_code_diff 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 show_code_diff. 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.
show_code_diff 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 →