List config variables and their values in a Jujutsu (jj) repository. Shows both user and repo-level configs by default. Parameters: name (Optional name of specific config option to list), includeDefaults (Optional flag to include default values), includeOverridden (Optional flag to include overri...
AI agents call config-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 only retrieves and displays configuration information from a Jujutsu repository. It performs no writes, deletions, or external command execution. The parameters (name, includeDefaults, includeOverridden, user, repo, repoPath, cwd) are all filtering/display options for the read operation.
From the tool's definition Tool description states it 'List config variables and their values' with parameters for filtering what to display. The verb 'list' and function of displaying/querying configuration indicates read-only retrieval with no modification or execution capability.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List config variables and their values in a Jujutsu (jj) repository. Shows both user and repo-level configs by default. Parameters: name (Optional name of specific config option to list), includeDefaults (Optional flag to include default values), includeOverridden (Optional flag to include overridden values), user (Optional flag to only show user-level config), repo (Optional flag to only show repo-level config), 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 config-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.
config-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 config-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 config-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.
config-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 →