AI agents call git-remote-list 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.
This tool retrieves information about Git remotes configured in a repository. It performs no modifications, deletions, or execution of arbitrary code—only querying and displaying existing configuration data. The parameters are purely informational (repo paths) with no capability to alter state. This is a classic Read category tool with minimal risk.
From the tool's definition Tool name is 'git-remote-list' and description states it 'List Git remotes in a Jujutsu (jj) repository' with only optional path parameters.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List Git remotes in a Jujutsu (jj) repository. Parameters: 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 git-remote-list: 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-list 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 git-remote-list 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-list. 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-list 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 →