publish_project · Prowpt MCP Server MCP: Risk & Policy

WHAT IT DOES

What publish_project does on Prowpt MCP Server

AI agents use publish_project to create or update resources in Prowpt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prowpt MCP Server environment.

WHY IT NEEDS A POLICY

Why publish_project needs a policy

Publishing a project is a state-modifying action that affects production systems and their accessibility. Although the sibling 'delete_asset' and 'delete_email_template' suggest destructive operations exist on this server, publishing itself is a reversible write operation that promotes code to live.

From the tool's definition The tool description states it "Publish the current draft to live (makes the app accessible via subdomain)" — this action creates or modifies the live state of a web application, transitioning it from draft to production.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_project Rate-limited

publish_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish_project": {
      "limits": [
        {
          "counter": "publish_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 publish_project

What does the publish_project tool do? +

Publish the current draft to live (makes the app accessible via subdomain). It is categorised as a Write tool in the Prowpt MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on publish_project? +

Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for publish_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 publish_project? +

publish_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit publish_project? +

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

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

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