Unset a config option in a Jujutsu (jj) repository. Removes from either user or repo config file. Parameters: name (Name of config option to unset), user (Optional flag to unset user-level config), repo (Optional flag to unset repo-level config), repoPath (Optional path to repo root or working di...
AI agents invoke config-unset to trigger actions in Jj. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
config-unset triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Unset a config option in a Jujutsu (jj) repository. Removes from either user or repo config file. Parameters: name (Name of config option to unset), user (Optional flag to unset user-level config), repo (Optional flag to unset 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 Execute tool in the Jj MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jj MCP server in PolicyLayer and add a rule for config-unset: 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-unset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the config-unset 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-unset. 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-unset 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 →