ReadReal vs Hype19 Jul 20262:174 min readMES & shop-floor systems

An AI Can Now Tell a Chip Factory Machine to STOP — Nobody Agreed Who's Allowed To

Your AI Just Got a Key to the Factory Floor (Nobody Scoped What It Can Break)

A machine's physical stop lever under a clear safety cover, the lever lit warm gold
The picture for this piece. Made for it: no people, no brands.

In plain words

A public server now lets an AI tell a chip factory machine to stop. Nobody agreed who is allowed to.

The server hands an AI ten tools for real factory equipment. Six only read. Four write: start, stop, abort, and change the recipe.

It ships with no safety warning.

It lands the same week Microsoft put AI agents into Word, Excel and Outlook. The same year, Gartner told manufacturers to demand this kind of connection.

The factory solved this thirty years ago. Every machine has a defined list of who may command it, and how.

The new connection skipped that list.

Picture it. Every machine already has a guest list at the door. The new server walked straight past the doorman.

Why it matters to you. Before you connect one more tool to your AI, list every command it could send, and mark which ones you would want a person to approve first.

Terms in this piece

MCP Model Context Protocol
A standard way to hand an AI model a set of tools it can call, such as reading a database or sending a command.

The number

4 OF 10

TOOLS THAT WRITE: START, STOP, ABORT, RECIPE · MCP SERVER · JULY 2026

What to do Monday

MCP connectors landed in the Microsoft 365 admin center and agents reached Word, Excel, PowerPoint and Outlook on July 15, 2026. Before you connect one more tool, open your AI and paste: "List every connected tool. For each one, say whether it can only READ, or whether it can WRITE, send, post, or spend. Flag every write tool." I ran it on my own setup — it flagged a connector that can create and modify live ad campaigns.

The honest caveat

Most factories keep their tools on isolated networks, so a public server cannot reach them unless someone wires it in. The danger is the missing permission model, not the server itself. The old rule book still applies once it is wired.

Your turn

Engineers — what's the worst thing you've seen a host command do to a tool that should have been in Local?

Argue with me on LinkedIn

Sources

The run's YouTube description carried no source list; these entries were recovered from the run's thesis file (MES_Thesis_who-is-allowed-to-say-stop.docx), which recorded the sources the piece was written from.

  1. PrimaryPublic MCP server exposes 10 tools over SEMI E30/E87/E40/E116/E191; 4 are write-capable (remote START/STOP/ABORT/PP-SELECT, equipment constants, process-job and carrier ops). No safety warning; validated against a simulator only.
  2. PressSECS/GEM adoption in semiconductor fabs: 95%+ of equipment.
  3. PrimaryGEM Control State Model: OFFLINE / ONLINE-LOCAL / ONLINE-REMOTE. In Local, the operator holds authority and the host can only observe. S2F21 carries remote commands (START/STOP/PP-SELECT).
  4. PrimaryMCP released by Anthropic November 2024; adopted through 2025 by OpenAI, Google and Microsoft; now the de-facto standard for connecting agents to tools and data.
  5. AnalystGartner 2026 Market Guide for MES (published 22 Mar 2026; Cunningham & Hestermann) stresses open architectures and MCP for agentic workflows.
  6. AnalystOnly about one-third of MES vendors can reference a live production AI use case.
  7. PrimaryMicrosoft 365: MCP-based Federated Copilot Connectors manageable in the admin center, and agents with MCP available in Word, Excel, PowerPoint and Outlook — 15 July 2026.
  8. PrimaryNSA AI Security Center Cybersecurity Information Sheet, “MCP: Security Design Considerations for AI-Driven Automation,” 20 May 2026. Warns adoption outpaced safeguards; names uncontrolled automated actions and absent input screening; recommends strict permission boundaries, process isolation and detailed logging of every tool action.
  9. PrimaryOX Security, April 2026: architectural RCE baked into the official MCP SDKs (Python, TypeScript, Java, Rust). ~200,000 vulnerable instances, 150M+ package downloads, 7,000+ publicly reachable servers. 30+ disclosures, 10+ High/Critical CVEs. Anthropic declined the architectural fix, calling the behaviour “expected.”
  10. AnalystMESA International guidance, 8 Dec 2025 (Makhija): MCP resolves N×M integration sprawl across sensors, MES logs, ERP and control systems; explicitly flags safety validation for agent commands and latency in time-critical applications as open challenges.
  11. AnalystLNS Research created a new top-level “Agentic Operations” category in its March 2026 Industrial AI Market Landscape — the shift from insight to action.
  12. PrimaryAthena Technology Solutions launched FabOrchestrator (15 Apr 2026), layering LLM agents on Siemens Opcenter and Critical Manufacturing MES for reporting, support triage, modeling and code generation.
Read the full script (313 words)
Ask an AI to book a meeting, it books it. Ask it to STOP a machine in a chip factory… and nobody can tell you who's allowed to say yes. Right now there's a public server handing an AI ten tools for real fab equipment. Six read. Four WRITE — start, stop, abort, change the recipe. No safety warning. Who approved that? Your AI reaches everything through a protocol called MCP. Gartner now tells manufacturers to demand it from their MES vendor. Last week it landed in Word, Excel and Outlook. So what's missing? Your fab already solved this. Ninety-five percent of your tools speak SECS/GEM — and GEM has what MCP never had. A control state. Offline. Online-local. Online-remote. A tool in local mode REFUSES the host. See the gap? MCP tells your agent what it CAN call. GEM tells the machine whether it's ALLOWED to obey. One's a menu. The other's a lock. Reading your fab with AI? Do it. It's WRITE nobody scoped. So when someone demos an agent on your floor, ask one thing. What can it change — and what says no? Now — your FabSpeak Tip of the Week. Stop CONNECTING tools to your AI. Start auditing them. Microsoft just put MCP connectors in the Microsoft 365 admin center, and agents landed in Word, Excel and Outlook on July fifteenth. So before you add one more, open your AI and paste this. "List every connected tool. For each one, say whether it can only READ, or whether it can WRITE, send, post, or spend. Flag every write tool." I ran it on my own setup today. It flagged a connector that can create and modify live ad campaigns — real money — which I'd completely forgotten I'd connected. Save this. Run it before Monday. That's FabSpeak. One thing a week from where the chips actually get made. Follow, and I'll keep bringing them.