delete_environment

3 registry entries were observed exposing a tool named delete_environment — 3 of them as a privileged capability (a name matching exec / write / delete keywords).

Spelled delete_environment, delete-environment in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @reachpad/mcpprivilegedverified
   trust 85/100 · AMCP serverobserved 2026-08-12 · static extraction
   Coding agents build full-stack apps in persistent workspaces and share them by link.
2. io.github.configcat/mcp-serverprivilegedverified
   trust 85/100 · AMCP serverobserved 2026-06-13 · static extraction
   Enables AI agents to interact with ConfigCat, a feature flag service for teams.
3. @abhishekmcp/httpprivileged
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   MCP server for HTTP/REST APIs — ad-hoc requests plus saved collections and environments, with a required host allowlist and SSRF protection,

All indexed toolsSearch the registry for delete_environment