--- title: "Discussion on \"AI Is Getting a Body. Here's What That Means.\" | Hashnode" description: "Discussion on \"AI Is Getting a Body. Here's What That Means.\". Build the Brain — Series Intro" url: "https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9" --- [Feed](https://hashnode.com/feed) / Discussion # [AI Is Getting a Body. Here's What That Means.](https://techmyway.hashnode.dev/ai-is-getting-a-body-here-s-what-that-means?utm_source=hashnode&utm_medium=feed) Build the Brain — Series Intro Jul 21 · 8 min read · techmyway.hashnode.dev Updated Jul 24 Read the article - [#agentic-ai](https://hashnode.com/tag/agentic-ai) - [#ai](https://hashnode.com/tag/ai) - [#llm](https://hashnode.com/tag/llm) - [#large-language-models](https://hashnode.com/tag/large-language-models) - [#agents](https://hashnode.com/tag/agents) ## Written by [Kavya Sree Kammari](https://hashnode.com/@CosmosAtom) @CosmosAtom · Bengaluru [View profile](https://hashnode.com/@CosmosAtom) Tech, but with personality AI/Platform Engineer @ SAP Labs and fresh graduate from Amrita Vishwa Vidyapeetham. Love robotics and AI. Building AI frameworks. Dopamine to me is learning something new every day. I even have an agent deployed on GCP for that. ## Responses 8 Markdown supported · ⌘↵ to post [Ishvarya](https://hashnode.com/@ishvarya) [Jul 23](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a6231b2a8c5bb6a7d558468) Hey Kavya, Loved the way you’ve structured the article. The fact that you started with what’s already there (LLMs) to what’s being adopted ( Agentic AI) and then you go on to connect the dots with the “how” part of it - puts the whole article into perspective! Can’t wait for the next one… [Kavya Sree Kammari](https://hashnode.com/@CosmosAtom) [Jul 23](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a6231b2a8c5bb6a7d558468#reply-6a624b9e16eef162aac93da6) Thank you, Ishvarya! I really appreciate the kind feedback and so glad the flow made sense. Next article is already in the works! ✨ [Kartik N V J K](https://hashnode.com/@kartik-nvj) [Jul 23](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a6223032cbf85657edaf90e) The "read the guidebook the airline publishes" analogy for MCP is the clearest framing of it I've come across. It captures that the agent isn't hardcoded against one API, it discovers capabilities a provider chose to expose, which is what makes the pattern scale across tools. Where do you see the boundary landing on what a provider should and shouldn't expose through it? [Kavya Sree Kammari](https://hashnode.com/@CosmosAtom) [Jul 23](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a6223032cbf85657edaf90e#reply-6a622f418a697416a8cc0b12) Great observation Kartik! The rule of thumb I'd use: expose actions, not infrastructure. A provider should publish what it can do (search flights, book, cancel, check status), not raw database access or internal system internals. The boundary is capability vs infrastructure. And this is actually a real security conversation happening right now. If a provider exposes too much through an MCP, a poorly-scoped agent could read data it shouldn't, trigger unintended actions, or become an attack surface for prompt injection. Production teams are genuinely cautious about this — which is part of why adoption has been slower than the hype suggests. There's also an interesting industry shift happening: until recently, there was a whole ecosystem of startups, consultants, and freelancers whose job was to build the custom product or infra layer for your specific AI usecase — designing how AI plugs into your business end to end. MCP is quietly threatening that. When the protocol is standardised and any AI can discover what your service does, that bespoke integration business gets a lot harder to justify. Going deep on this in the MCP dedicated post later in the series. [Yasasree Lasya](https://hashnode.com/@lasya904) [Jul 21](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a5fa61db6c1e3d3272a4494) My laziness is my JARVIS moment which made me fall in love with the idea of something else doing the work for me 🤧😂 [Kavya Sree Kammari](https://hashnode.com/@CosmosAtom) [Jul 23](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a5fa61db6c1e3d3272a4494#reply-6a622f5b8a697416a8cc0d23) My laziness brought me into CS too honestly 🤣. If something can be automated, it should be. [Siddhesh Inamdar](https://hashnode.com/@siddhesh-inamdar) [Jul 29](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a5fa61db6c1e3d3272a4494#reply-6a6a20dc8af164481da06b28) Hi Kavya, Lasya shared me your blogsite. Really insightful demonstration of the ReAct loop. I see how you compared MCP to USB C. Ingenious. [Kavya Sree Kammari](https://hashnode.com/@CosmosAtom) [Jul 31](https://hashnode.com/posts/ai-is-getting-a-body-here-s-what-that-means/6a5f8edaaf4356122f7a7dd9/comment/6a5fa61db6c1e3d3272a4494#reply-6a6c15cd7ff5c4bc6705a25e) Hey Siddhesh! Thanks a lot! Glad you liked the article and the MCP/USB-C comparison. Felt like the most practical way to explain it! Appreciate you taking the time to read it.