juno_functions_eject · Junobuild MCP: Risk & Policy

WHAT IT DOES

What juno_functions_eject does on Junobuild

AI agents use juno_functions_eject 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_functions_eject needs a policy

This tool creates new files (scaffolding/boilerplate) in the project. It's a Write operation as it generates files, but these are new scaffold files rather than modifying existing critical data. The blast radius is low since it only creates boilerplate code files that a developer would then edit.

From the tool's definition Generate the required files to begin developing serverless functions in your project. Scaffolds boilerplate for Rust, TypeScript, or JavaScript functions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

juno_functions_eject Rate-limited

juno_functions_eject 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_functions_eject": {
      "limits": [
        {
          "counter": "juno_functions_eject_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_functions_eject

What does the juno_functions_eject tool do? +

Generate the required files to begin developing serverless functions in your project. Scaffolds boilerplate for Rust, TypeScript, or JavaScript functions. Alias:. 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_functions_eject? +

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

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

Can I rate-limit juno_functions_eject? +

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

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

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