deploy
Deploy or update a project on Deloc. If an app with the same name already exists, it will be updated in place — do NOT delete and recreate apps. Redeploying preserves the same URL and settings. Set password to a string to use that password, or to true/
This record as markdown: /tools/deloc-mcp/deploy.md
What deploy does on Deloc
AI agents invoke deploy to trigger actions in Deloc. 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 deploy is rated High
The deploy tool executes a deployment operation that launches live infrastructure and modifies external state (creates or updates projects on Deloc, generates public URLs, applies settings). While not immediately destructive (redeployment preserves URLs), it is an Execute operation because it runs code/triggers external services whose side effects depend on what is deployed.
From the tool's definition Tool description states 'Deploy or update a project on Deloc' and 'get a live URL back' — this triggers external deployment operations whose effects depend on arguments (project name, code, settings, password).
Attacks that exploit this kind of access
The rule that runs deploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deploy, this is the rule to start with:
deploy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every deploy call is checked against it from then on.
Questions about deploy
Deploy or update a project on Deloc. If an app with the same name already exists, it will be updated in place — do NOT delete and recreate apps. Redeploying preserves the same URL and settings. Set password to a string to use that password, or to true/. It is categorised as a Execute tool in the Deloc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deloc MCP server in PolicyLayer and add a rule for deploy: 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 Deloc. Nothing to install.
deploy 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 deploy 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 deploy. 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.
deploy is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue