Remove a Git remote from a Jujutsu (jj) repository. Parameters: name (Name of the remote to remove), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in).
AI agents call git-remote-remove to permanently remove resources in Jj — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a Git remote is an irreversible configuration change that deletes the remote reference and all associated tracking metadata from the repository. This cannot be undone without manually re-adding the remote and its tracking branches, making it a destructive operation. Misuse could sever the repository's connection to upstream remotes, disrupting collaboration and CI/CD workflows.
From the tool's definition Remove a Git remote from a Jujutsu (jj) repository
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Remove a Git remote from a Jujutsu (jj) repository. Parameters: name (Name of the remote to remove), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in). It is categorised as a Destructive tool in the Jj MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jj MCP server in PolicyLayer and add a rule for git-remote-remove: 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.
git-remote-remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the git-remote-remove 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 git-remote-remove. 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.
git-remote-remove 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 →