stop_project

Stop a DenkOps deployment (containers stop and it goes offline). Reversible with start_project.

SERVERDenkopsai SOURCE@denkopsai/mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/denkopsai-mcp/stop-project.md

WHAT IT DOES

What stop_project does on Denkopsai

AI agents invoke stop_project 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.

RISK

Why stop_project is rated High

This tool executes an operation that stops a live deployment, taking containers offline. While the description indicates it is reversible via start_project, the action itself is an execution of infrastructure control (stopping containers) rather than data retrieval (Read), data modification (Write), or permanent deletion (Destructive).

From the tool's definition Tool description states: 'Stop a DenkOps deployment (containers stop and it goes offline). Reversible with start_project.' The action terminates running containers and takes a service offline, which is an external operational trigger with significant side…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_project 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 stop_project, this is the rule to start with:

stop_project Rate-limited

stop_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": {
    "stop_project": {
      "limits": [
        {
          "counter": "stop_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every stop_project call is checked against it from then on.

FAQ

Questions about stop_project

What does the stop_project tool do? +

Stop a DenkOps deployment (containers stop and it goes offline). Reversible with start_project. 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.

What parameters does stop_project accept? +

stop_project accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on stop_project? +

Register the Denkopsai MCP server in PolicyLayer and add a rule for stop_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 Denkopsai. Nothing to install.

What risk level is stop_project? +

stop_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_project? +

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

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

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

KEEP EXPLORING

More on Denkopsai, and thousands of servers like it.

This server

All 28 Denkopsai tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →