---
title: "Discussion on \"Read-Write MCP: Three Cloud Operations We Stopped Letting AI Touch After 90 Days\" | Hashnode"
description: "Discussion on \"Read-Write MCP: Three Cloud Operations We Stopped Letting AI Touch After 90 Days\". The read-only MCP server work shipped clean. AI agents could read tags, search logs, query costs, walk topology. Operators saved hours per incident. The next question was obvious: which writes can the"
url: "https://hashnode.com/posts/read-write-mcp-three-cloud-operations-we-stopped-letting-ai-touch-after-90-days/6a040a0552a9c969d6053e43"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Read-Write MCP: Three Cloud Operations We Stopped Letting AI Touch After 90 Days](https://zopdev.hashnode.dev/read-write-mcp-three-cloud-operations-we-stopped-letting-ai-touch-after-90-days?utm_source=hashnode&utm_medium=feed)

The read-only MCP server work shipped clean. AI agents could read tags, search logs, query costs, walk topology. Operators saved hours per incident. The next question was obvious: which writes can the

May 13 · 12 min read · zopdev.hashnode.dev  
Read the article

## Written by

[Muskan](https://hashnode.com/@muskanzop)

@muskanzop · Bangalore, India

  
[View profile](https://hashnode.com/@muskanzop)

Cloud Associate ,Exploring Cloud Infrastructure, FinOps & DevOps

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
