bookmark-delete

Delete an existing bookmark in a Jujutsu (jj) repository and propagate the deletion to remotes on the next push. Parameters: names (Names of bookmarks to delete), repoPath (Optional path to repo root or working directory), cwd (Optional working directory to run the command in).

Server Jj jj-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What bookmark-delete does on Jj

AI agents call bookmark-delete 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.

Why bookmark-delete needs a policy

This tool irreversibly deletes bookmarks and propagates those deletions to remote repositories. Once deleted and pushed, the action cannot be trivially reversed—it requires recovery operations or force-pushes.

From the tool's definition Tool name is 'bookmark-delete' and description explicitly states 'Delete an existing bookmark in a Jujutsu (jj) repository and propagate the deletion to remotes on the next push.' The word 'Delete' combined with propagation to remotes indicates an…

Risk signalsAdmin/system-level operation

Questions about bookmark-delete

What does the bookmark-delete tool do? +

Delete an existing bookmark in a Jujutsu (jj) repository and propagate the deletion to remotes on the next push. Parameters: names (Names of bookmarks to delete), 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.

How do I enforce a policy on bookmark-delete? +

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

bookmark-delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bookmark-delete? +

Yes. Add a rate_limit block to the bookmark-delete 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 bookmark-delete completely? +

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

bookmark-delete 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.