deploy_project · Otoinstall MCP: Risk & Policy

WHAT IT DOES

What deploy_project does on Otoinstall

AI agents invoke deploy_project 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_project needs a policy

deploy_project executes a deployment action on a live server, which is an external operation with side effects. While not immediately destructive or financial, deployment can disrupt services, modify production systems, and cause significant operational impact. The tool's design requires prior user confirmation (analyze_project + user sign-off), indicating awareness of its risk.

From the tool's definition Tool description states 'Deploy a project to a live server' — this triggers external operations (project deployment) whose effects depend on arguments and cannot be trivially undone.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_project Rate-limited

deploy_project 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_project": {
      "limits": [
        {
          "counter": "deploy_project_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_project

What does the deploy_project tool do? +

Deploy a project to a live server. IMPORTANT: You MUST call analyze_project first and show the analysis to the user. Only call this tool after the user confirms they want to proceed. 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_project? +

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

What risk level is deploy_project? +

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

Can I rate-limit deploy_project? +

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

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

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