juno_config_init · Junobuild MCP: Risk & Policy

WHAT IT DOES

What juno_config_init does on Junobuild

AI agents use juno_config_init 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_config_init needs a policy

This tool creates a configuration file on disk. When writeFile is true, it writes to the filesystem, which is a reversible Write action (the file can be overwritten or deleted). It doesn't execute commands, delete data irreversibly, or move money. The blast radius is medium since a misconfigured juno.config could affect satellite behavior when subsequently applied.

From the tool's definition Generate a juno.config file... Set writeFile to true to write the file directly to disk.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

juno_config_init Rate-limited

juno_config_init 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_config_init": {
      "limits": [
        {
          "counter": "juno_config_init_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_config_init

What does the juno_config_init tool do? +

Generate a juno.config file (TypeScript, JavaScript, or JSON). By default returns config content for preview. Set writeFile to true to write the file directly to disk. Then run juno_config_apply to push the config to your satellite. 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_config_init? +

Register the Junobuild MCP server in PolicyLayer and add a rule for juno_config_init: 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_config_init? +

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

Can I rate-limit juno_config_init? +

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

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

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