redeploy
Re-run the current version of a DenkOps project (applies staged env changes / restarts the app). No code re-upload; reuses the last build.
This record as markdown: /tools/denkopsai-mcp/redeploy.md
What redeploy does on Denkopsai
AI agents invoke redeploy to trigger actions in Denkopsai. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes |
Parameters from the server's own tool schema.
Why redeploy is rated High
Redeploy executes an operation on an external system (DenkOps infrastructure) that causes side effects: restarting an application and applying configuration changes. While not destructive or financial, this is clearly an Execute action as it triggers a process whose effects depend on the project state and staged changes.
From the tool's definition Tool performs 'Re-run the current version of a DenkOps project', 'applies staged env changes / restarts the app' - these are active operations that trigger external system behavior (app restart, environment application).
Attacks that exploit this kind of access
The rule that runs redeploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redeploy, this is the rule to start with:
redeploy 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 Denkopsai, apply this rule, and every redeploy call is checked against it from then on.
Questions about redeploy
Re-run the current version of a DenkOps project (applies staged env changes / restarts the app). No code re-upload; reuses the last build. It is categorised as a Execute tool in the Denkopsai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
redeploy accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for redeploy: 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 Denkopsai. Nothing to install.
redeploy 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 redeploy 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 redeploy. 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.
redeploy is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
Across the catalogue