delete_review_app_environments

Schedule deletion of stopped review-app environments one week later; dry_run defaults to true and actual scheduling requires dry_run=false

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-review-app-environments.md

WHAT IT DOES

What delete_review_app_environments does on Gitlab Mcp

AI agents call delete_review_app_environments to permanently remove resources in Gitlab Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_review_app_environments is rated Critical

Permanently deletes cloud infrastructure environments; high blast radius if misconfigured targets production infrastructure.

From the tool's definition Schedule deletion of stopped review-app environments; dry_run defaults to true

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_review_app_environments safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_review_app_environments, this is the rule to start with:

delete_review_app_environments Hidden

delete_review_app_environments is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_review_app_environments"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_review_app_environments

What does the delete_review_app_environments tool do? +

Schedule deletion of stopped review-app environments one week later; dry_run defaults to true and actual scheduling requires dry_run=false. It is categorised as a Destructive tool in the Gitlab Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_review_app_environments? +

Register the Gitlab MCP server in PolicyLayer and add a rule for delete_review_app_environments: 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 Gitlab Mcp. Nothing to install.

What risk level is delete_review_app_environments? +

delete_review_app_environments is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_review_app_environments? +

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

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

delete_review_app_environments is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 279 Gitlab tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →