juno_hosting_deploy · Junobuild MCP: Risk & Policy

WHAT IT DOES

What juno_hosting_deploy does on Junobuild

AI agents invoke juno_hosting_deploy to trigger actions in Junobuild. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why juno_hosting_deploy needs a policy

Deployment operations execute code/infrastructure changes whose effects depend on arguments (which app, version, configuration to deploy). While not immediately destructive or financial, deployments can cause service disruptions, resource consumption, or unintended behavior changes.

From the tool's definition Tool name 'juno_hosting_deploy' and description 'Deploy your app' indicate execution of a deployment operation that triggers external infrastructure changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

juno_hosting_deploy Rate-limited

juno_hosting_deploy stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_hosting_deploy": {
      "limits": [
        {
          "counter": "juno_hosting_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_hosting_deploy

What does the juno_hosting_deploy tool do? +

Deploy your app. It is categorised as a Execute tool in the Junobuild MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on juno_hosting_deploy? +

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

juno_hosting_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit juno_hosting_deploy? +

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

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

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