deploy_project · Prowpt MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_project does on Prowpt MCP Server

AI agents invoke deploy_project to trigger actions in Prowpt MCP Server. 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

Deploying a project is an operational action that executes code or infrastructure changes on external hosting. While not inherently destructive (the previous version may still be recoverable), it is an Execute-class action because it triggers external processes and changes the state of production systems.

From the tool's definition Tool performs 'Deploy project to hosting' — this triggers external operations (deployment pipeline, server updates, infrastructure changes) whose effects depend on which project is specified as an argument.

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 Prowpt MCP Server, so you can run agents against it safely.

FAQ

Questions about deploy_project

What does the deploy_project tool do? +

Deploy project to hosting. It is categorised as a Execute tool in the Prowpt MCP Server 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 Prowpt MCP Server 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 Prowpt MCP Server. 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 Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

deploy_project is one line of Prowpt MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →