# Change, resize or clean up live resources

> Change, resize or clean up live resources: 0 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Cloud & infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/infrastructure.change-live-resources/
- Markdown: https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/infrastructure.change-live-resources/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 10 | 14 | 5 |

## What counts as done

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

How agents ask for it: resize the database volume; clean up unused resources; scale this service; delete the old staging environment

## Does the job, with a limit

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

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

- not this job: neckbeard (David Beale (individual, GitHub account bealesh)): It never applies changes to live resources itself.

## What stops agents finishing

- any token can delete any resource, whatever it was made for
- staging and production share a resource the agent cannot see
- no confirmation step on delete once a write scope is granted

## Around it

Before: infrastructure.inspect-debug. After: observability.verify-deploy.

## Where this comes from

Weight 14 of 100 in Cloud & 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

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

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
