git-export

Update the underlying Git repo with changes made in the Jujutsu (jj) repository. Useful for syncing jj changes back to Git. Parameters: repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in).

Server Jj jj-mcp-server
Category Write
Risk class Medium
Parameters 00 required

What git-export does on Jj

AI agents use git-export 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.

Why git-export needs a policy

This tool writes changes to a Git repository by exporting jj changes. While the changes themselves are reversible (Git commits can be undone, branches can be reset), the tool modifies version control state in potentially significant ways.

From the tool's definition Tool description states it will 'Update the underlying Git repo with changes made in the Jujutsu (jj) repository' and is 'Useful for syncing jj changes back to Git'.

Risk signalsAdmin/system-level operation

Questions about git-export

What does the git-export tool do? +

Update the underlying Git repo with changes made in the Jujutsu (jj) repository. Useful for syncing jj changes back to Git. Parameters: 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.

How do I enforce a policy on git-export? +

Register the Jj MCP server in PolicyLayer and add a rule for git-export: 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.

What risk level is git-export? +

git-export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git-export? +

Yes. Add a rate_limit block to the git-export 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 git-export completely? +

Set action: deny in the PolicyLayer policy for git-export. 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 git-export? +

git-export 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.