Deploy/publish a repl
AI agents invoke create_deployment to trigger actions in Replit 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.
Deploying/publishing a repl triggers an external operation that runs the repl's code on Replit's infrastructure and makes it publicly accessible. This is an Execute-category action as it initiates a live deployment process with real-world effects (serving traffic, consuming compute resources). It spans Write but the act of publishing/running code in production makes Execute the most appropriate category.
From the tool's definition Deploy/publish a repl
Attacks that exploit this kind of access
Deploy/publish a repl. It is categorised as a Execute tool in the Replit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Replit MCP Server MCP server in PolicyLayer and add a rule for create_deployment: 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 Replit MCP Server. Nothing to install.
create_deployment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_deployment 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.
Set action: deny in the PolicyLayer policy for create_deployment. 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.
create_deployment is provided by the Replit MCP Server MCP server (nova-3951/replit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →