Restore paths from another revision in a Jujutsu (jj) repository. Can undo changes to specific files by restoring them to their previous state. Parameters: source (Optional source revision to restore from, defaults to parent), destination (Optional destination revision to restore into, defaults t...
AI agents use restore to create or update resources in Jj — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jj environment.
The restore tool modifies file contents by reverting them to previous states, which is a write operation. While it restores rather than creates new content, it still changes the working copy or a destination revision. It is reversible (can be undone by restoring to a different revision), so it does not qualify as Destructive.
From the tool's definition Tool description states it can "undo changes to specific files by restoring them to their previous state" and mentions parameters for source/destination revisions and paths. This modifies file content in the repository.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Restore paths from another revision in a Jujutsu (jj) repository. Can undo changes to specific files by restoring them to their previous state. Parameters: source (Optional source revision to restore from, defaults to parent), destination (Optional destination revision to restore into, defaults to working copy), paths (Paths to restore), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in). It is categorised as a Write tool in the Jj MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jj MCP server in PolicyLayer and add a rule for restore: 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.
restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore 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 restore. 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.
restore 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 →