juno_create_project · Junobuild MCP: Risk & Policy

WHAT IT DOES

What juno_create_project does on Junobuild

AI agents use juno_create_project to create or update resources in Junobuild — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Junobuild environment.

WHY IT NEEDS A POLICY

Why juno_create_project needs a policy

This tool creates new project files and configuration, which are reversible changes (files can be deleted, projects can be removed). It does not execute arbitrary code post-creation, delete existing resources, move money, or trigger external operations with uncontrolled effects. The action is a standard Write operation: creating structured data artifacts.

From the tool's definition Tool name 'juno_create_project' and description 'Scaffold a new Juno project' indicates creation of new project resources. Description explicitly states it creates frontend scaffolding, adds SDK and config files—all reversible modifications to the file system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

juno_create_project Rate-limited

juno_create_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "juno_create_project": {
      "limits": [
        {
          "counter": "juno_create_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Junobuild, so you can run agents against it safely.

FAQ

Questions about juno_create_project

What does the juno_create_project tool do? +

Scaffold a new Juno project. Uses Vite to create the frontend, then adds Juno SDK and config. Does NOT use the interactive create-juno CLI. It is categorised as a Write tool in the Junobuild MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on juno_create_project? +

Register the Junobuild MCP server in PolicyLayer and add a rule for juno_create_project: 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.

What risk level is juno_create_project? +

juno_create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit juno_create_project? +

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

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

juno_create_project 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.