Delete a package (requires authentication and scope admin, package must have no versions).
AI agents call jsr_delete_package to permanently remove resources in JSR MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a package, which cannot be undone. While it has a guard (package must have no versions), the delete operation itself is destructive in nature. The blast radius is high because an AI agent could inadvertently remove important packages from the registry, affecting downstream users and projects that depend on them.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a package'. The operation is irreversible and removes a package entirely from the registry.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Delete a package (requires authentication and scope admin, package must have no versions). It is categorised as a Destructive tool in the JSR MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JSR MCP server in PolicyLayer and add a rule for jsr_delete_package: 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 JSR MCP. Nothing to install.
jsr_delete_package is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jsr_delete_package 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 jsr_delete_package. 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.
jsr_delete_package is provided by the JSR MCP server (wyattjoh/jsr-mcp). 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 →