git-remote-rename · Jj MCP: Risk & Policy

WHAT IT DOES

What git-remote-rename does on Jj

AI agents use git-remote-rename 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 IT NEEDS A POLICY

Why git-remote-rename needs a policy

This tool modifies repository configuration by renaming a Git remote reference. Remote configuration changes are reversible (can be renamed back) and do not alter actual code, commits, or data. The operation is a metadata write with minimal blast radius—it affects only the local repository's remote alias configuration.

From the tool's definition Tool description states it 'Rename[s] a Git remote in a Jujutsu (jj) repository' with parameters for oldName and newName. The term 'rename' indicates a reversible modification to repository metadata.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git-remote-rename Rate-limited

git-remote-rename stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git-remote-rename": {
      "limits": [
        {
          "counter": "git-remote-rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jj, so you can run agents against it safely.

FAQ

Questions about git-remote-rename

What does the git-remote-rename tool do? +

Rename a Git remote in a Jujutsu (jj) repository. Parameters: oldName (Current name of the remote), newName (New name for the remote), 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-remote-rename? +

Register the Jj MCP server in PolicyLayer and add a rule for git-remote-rename: 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-remote-rename? +

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

Can I rate-limit git-remote-rename? +

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

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

git-remote-rename 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.