Show changes to the repository in an operation of a Jujutsu (jj) repository. Displays what changed in the specified operation. Parameters: operation (Operation to show, defaults to latest), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the comm...
AI agents call operation-show to retrieve information from Jj without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool purely queries and displays information about a version control operation's changes. It has no side effects on the repository or its contents. This is a straightforward read operation similar to 'git log' or 'git show'. The parameters allow specifying which operation to inspect and where the repository is located, but do not enable modifications or destructive actions.
From the tool's definition Tool description states it 'Displays what changed in the specified operation' - a display/show operation that retrieves and presents information about repository changes without modifying state.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Show changes to the repository in an operation of a Jujutsu (jj) repository. Displays what changed in the specified operation. Parameters: operation (Operation to show, defaults to latest), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in). It is categorised as a Read tool in the Jj MCP Server, which means it retrieves data without modifying state.
Register the Jj MCP server in PolicyLayer and add a rule for operation-show: 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 Jj. Nothing to install.
operation-show 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 operation-show 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 operation-show. 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.
operation-show is provided by the Jj MCP server (jj-mcp-server). 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 →