deploy_zip · Otoinstall MCP: Risk & Policy

WHAT IT DOES

What deploy_zip does on Otoinstall

AI agents invoke deploy_zip to trigger actions in Otoinstall. 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 deploy_zip needs a policy

This tool executes a deployment operation on live servers, which is inherently an Execute-category action. The severity is high because a malicious ZIP file or incorrect deployment could cause widespread outages, data corruption, or compromise of production systems. It is not Destructive (no explicit deletion) and not Financial, but it does trigger external operations with significant blast radius.

From the tool's definition Tool description states 'Deploy an existing ZIP file to a live server' — this triggers external deployment operations whose effects depend on the ZIP file contents and target server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_zip Rate-limited

deploy_zip 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": {
    "deploy_zip": {
      "limits": [
        {
          "counter": "deploy_zip_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 Otoinstall, so you can run agents against it safely.

FAQ

Questions about deploy_zip

What does the deploy_zip tool do? +

Deploy an existing ZIP file to a live server via OtoInstall. Use this when you already have a ZIP file ready. It is categorised as a Execute tool in the Otoinstall MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_zip? +

Register the Otoinstall MCP server in PolicyLayer and add a rule for deploy_zip: 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 Otoinstall. Nothing to install.

What risk level is deploy_zip? +

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

Can I rate-limit deploy_zip? +

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

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

deploy_zip is provided by the Otoinstall MCP server (otoinstall-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.