{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/infrastructure.change-live-resources/",
    "json": "https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 8 | 10 | 14 | 5 |\n\n## What counts as done\n\nOnly the named resource in the named environment changes; the tool shows the change before making it (dry run or plan), a destructive step waits for a person's approval, and the result is read back.\n\nHow agents ask for it: resize the database volume; clean up unused resources; scale this service; delete the old staging environment\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **AWS MCP Servers (Amazon Web Services, Inc.)**: REQUIRE_MUTATION_CONSENT asks for consent before writes and IAM limits scope, but both safety flags default to false and there is no plan or dry-run summary of a change.\n- **Azure MCP Server (Microsoft Corporation)**: Writes run under the caller's RBAC with no confirmation step; the README warns that autonomous clients may perform destructive actions, and there is no dry run.\n- **Cloudflare CLI (cf) (Cloudflare, Inc.)**: --dry-run prints the request as JSON, and in non-interactive sessions destructive commands abort without --force; but the abort exits 0, and the agent can pass --force itself, so no person approves.\n- **Cloudflare MCP Servers (Cloudflare, Inc.)**: Writes need a scope that the client is asked to add on insufficient_scope, but once granted there is no per-call confirmation or dry run.\n- **DigitalOcean MCP Server (DigitalOcean, LLC)**: Custom-scope tokens can narrow what a token may touch, but delete tools such as apps-delete run with no confirmation step or dry run.\n- **Netlify API + MCP (Netlify, Inc.)**: Draft deploys preview a change before publishing, but tokens can't be narrowed to one site or environment and deletes have no confirmation step.\n- **Railway MCP Server (Railway Corporation)**: The local server returns a preview and requires confirm: true for destructive tools, but tokens carry no per-resource scope: acc-01's domain token deleted a volume shared with production, and acc-02 reports Railway's agent wiping a database.\n- **Render MCP Server (Render Services, Inc.)**: Changes are limited to triggering deploys and updating environment variables, with no deletes, but there is no preview of a change and no per-environment credential.\n- **Terraform MCP Server (HashiCorp, Inc. (an IBM Company))**: plan_only and get_plan_details show the plan before action_run applies it, and applies, deletes and force unlock need ENABLE_TF_OPERATIONS; but create_workspace and update_workspace, marked destructive, are not behind that flag.\n\n- not this job: neckbeard (David Beale (individual, GitHub account bealesh)): It never applies changes to live resources itself.\n\n## What stops agents finishing\n\n- any token can delete any resource, whatever it was made for\n- staging and production share a resource the agent cannot see\n- no confirmation step on delete once a write scope is granted\n\n## Around it\n\nBefore: infrastructure.inspect-debug. After: observability.verify-deploy.\n\n## Where this comes from\n\nWeight 14 of 100 in Cloud \u0026 infrastructure: 5 of 32 accounts, four of them production or staging deletions (PocketOS on Railway, the Terraform destroy on AWS); the strongest failure evidence in the category\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/infrastructure.change-live-resources.json, or the MCP tool get_use_case with id infrastructure.change-live-resources. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Change, resize or clean up live resources",
        "url": ""
      }
    ],
    "description": "Change, resize or clean up live resources: 0 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Cloud \u0026 infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Change, resize or clean up live resources",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/infrastructure.change-live-resources/",
    "published": "",
    "section": "agents",
    "title": "Change, resize or clean up live resources | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/infrastructure.change-live-resources/"
  },
  "tokens": {
    "markdown": 1100,
    "slim": 330
  },
  "version": 1
}
