Remove stale frontend files from your satellite that are no longer in your build output. Use --dry-run to preview which files would be deleted without actually deleting them.
AI agents call juno_hosting_prune to permanently remove resources in Junobuild — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes files from a satellite deployment without the ability to undo the action. While the --dry-run flag allows preview, the primary function is file deletion, making it Destructive rather than Write. The high severity reflects the potential for unintended data loss if an AI agent prunes incorrect files from a live hosting environment.
From the tool's definition Remove stale frontend files from your satellite that are no longer in your build output. The tool irreversibly deletes data ('Remove...files') with a --dry-run preview option, indicating the actual operation is destructive.
Attacks that exploit this kind of access
Remove stale frontend files from your satellite that are no longer in your build output. Use --dry-run to preview which files would be deleted without actually deleting them. It is categorised as a Destructive tool in the Junobuild MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Junobuild MCP server in PolicyLayer and add a rule for juno_hosting_prune: 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 Junobuild. Nothing to install.
juno_hosting_prune 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 juno_hosting_prune 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 juno_hosting_prune. 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.
juno_hosting_prune is provided by the Junobuild MCP server (junobuild-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 →