// SCAN REPORT

Junobuild

18 tools. 13 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

13 can modify or destroy data

5 read-only

18 tools total

Community server · catalogue entry verified 30/06/2026

How to control Junobuild ↓

TOOL MAP

What Junobuild exposes to your agents

Read (5) Write / Execute (11) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Junobuild tools

Destructive · High juno_hosting_clear The tool irreversibly deletes deployed application assets (frontend files) from a satellite. Destructive · High juno_hosting_prune This tool permanently deletes files from a satellite deployment without the ability to undo the action. Execute · High juno_functions_build Building serverless functions involves executing build scripts, transpilation, and code transformation processes. Execute · High juno_hosting_deploy Deployment operations execute code/infrastructure changes whose effects depend on arguments (which app, version, configuration to deploy).

13 of Junobuild's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Junobuild

PolicyLayer is an MCP gateway — it sits between your AI agents and Junobuild, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "juno_hosting_clear": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "juno_changes_reject": {
    "limits": [
      {
        "counter": "juno_changes_reject_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "juno_auth_status": {
    "limits": [
      {
        "counter": "juno_auth_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Junobuild — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON JUNOBUILD →

Instant setup, no code required.

FULL CATALOGUE

All 18 Junobuild tools

DESTRUCTIVE 2 tools

Destructive juno_hosting_clear Remove frontend files (JS, HTML, CSS, etc.) from your satellite. This does NOT remove user-uploaded files from Destructive juno_hosting_prune Remove stale frontend files from your satellite that are no longer in your build output. Use --dry-run to prev

EXECUTE 5 tools

Execute juno_changes_apply Apply a submitted change by its ID. Optionally create a snapshot before applying and verify the change hash fo Execute juno_functions_build Build your serverless functions. Supports Rust, TypeScript, and JavaScript. The CLI auto-detects the language Execute juno_functions_upgrade Upgrade your satellite Execute juno_hosting_deploy Deploy your app Execute juno_run Run a custom JavaScript or TypeScript script in the CLI context. The script has access to the authenticated Ju

WRITE 6 tools

Write juno_changes_reject Reject a submitted change by its ID. This prevents the change from being applied. Optionally verify the change Write juno_config_apply Apply the current juno.config file to your satellite. This is required after modifying settings like storage h Write juno_config_init Generate a juno.config file (TypeScript, JavaScript, or JSON). By default returns config content for preview. Write juno_create_project Scaffold a new Juno project. Uses Vite to create the frontend, then adds Juno SDK and config. Does NOT use the Write juno_functions_eject Generate the required files to begin developing serverless functions in your project. Scaffolds boilerplate fo Write juno_functions_publish Publish a new version of your serverless functions to the satellite. Optionally submit as a pending change wit

READ 5 tools

Read juno_auth_status Display the current authenticated profile, access key, and links to your satellite. Use this to verify authent Read juno_changes_list List all submitted or applied changes to your module. By default shows only submitted (pending) changes. Use - Read juno_docs Fetch Juno documentation from GitHub repo. Full docs: https://github.com/junobuild/docs/tree/main/docs. Topics Read juno_status Check the status of your modules (satellites, orbiters). Shows health, deployment status, and more. Read juno_version Show the current versions of the Juno CLI and emulator (if running). Use --version flag.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Junobuild

Can an AI agent delete data through the Junobuild MCP server? +

Yes. The Junobuild server exposes 2 destructive tools including juno_hosting_clear, juno_hosting_prune. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Junobuild? +

The Junobuild server has 6 write tools including juno_changes_reject, juno_config_apply, juno_config_init. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Junobuild.

How many tools does the Junobuild MCP server expose? +

18 tools across 4 categories: Destructive, Execute, Read, Write. 5 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Junobuild? +

Register the Junobuild MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Junobuild tool call.

Deterministic rules across all 18 Junobuild tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON JUNOBUILD →

Instant setup, no code required.

18 Junobuild tools catalogued and risk-classified — across an index of 43,000+ MCP servers.