// MCP TOOL REFERENCE

deploy_project

Admin/system-level operation

Part of the Ilumin MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke deploy_project to trigger processes or run actions in Ilumin. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON DEPLOY_PROJECT

deploy_project can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

ilumin.yaml

tools:
  deploy_project:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Ilumin policy for all 13 tools.

// DETAILS

Tool Name deploy_project

Category Execute

MCP Server Ilumin MCP Server

Risk Level High

// MORE ILUMIN TOOLS

Write install_app Write install_catalog_app Write manage_domain Write rebuild_app Write update_app Read get_app_env Read get_app_logs Read get_catalog_app_documentation

View all 13 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like deploy_project have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records getting_started

// IN CONTEXT OF HIGH RISK

deploy_project is one of the high-risk operations in Ilumin. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the deploy_project tool do? +

Deploys a local project to Ilumin Cloud. It automatically zips the project (ignoring node_modules, .git, etc.) and uploads it. IMPORTANT: Ensure a 'Dockerfile' exists in the project root before calling this tool.. It is categorised as a Execute tool in the Ilumin 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? +

Add a rule in your Intercept YAML policy under the tools section for deploy_project. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ilumin MCP server.

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 Intercept 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 Intercept 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 Ilumin MCP server (ilumin-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

deploy_project

Let agents act without letting them run wild.