Remove frontend files (JS, HTML, CSS, etc.) from your satellite. This does NOT remove user-uploaded files from custom collections — only the deployed app assets.
AI agents call juno_hosting_clear 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.
The tool irreversibly deletes deployed application assets (frontend files) from a satellite. While it explicitly excludes user-uploaded files, it permanently removes the production app code/assets, which cannot be undone without a rebuild/redeploy.
From the tool's definition Remove frontend files (JS, HTML, CSS, etc.) from your satellite. This does NOT remove user-uploaded files from custom collections — only the deployed app assets.
Attacks that exploit this kind of access
Remove frontend files (JS, HTML, CSS, etc.) from your satellite. This does NOT remove user-uploaded files from custom collections — only the deployed app assets. 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_clear: 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_clear 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_clear 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_clear. 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_clear 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 →