How to Build an MCP Server to Inject Security Context into AI Agents

When non-technical employees can spin up fully functioning apps in days and AI agents are running parallel workflows that babysit their own pull requests, the traditional SDLC is dead. In this episode, Ashish sits down with Prahathess Rengasamy, Senior Security Engineer at SpaceX AI, to discuss how the staggering compression of development time requires an entirely new approach to security engineering. Prahathess explains why legacy 10-minute PR wait times are incompatible with multi-agent workflows, and how security teams can build internal Model Context Protocol (MCP) servers to inject compliance and security guardrails directly into an agent's context window. We unpack the differences between Q&A chatbots and autonomous coding agents, the critical need to preserve foundational preventative cloud controls (like AWS SCPs and GCP Org Policies), and why holding an autonomous machine accountable for management decisions is a critical architectural flaw. Finally, Prahathess breaks down the "build vs. buy" debate, revealing how small security teams can leverage AI to rapidly deploy internal platforms and paved roads that previously took months to engineer.

Questions asked:

(00:00) Introduction: Compressing the Software Development Life Cycle (SDLC)(01:50) Prahathess Rengasamy’s Background (Block, Apple, SpaceX AI)(02:50) How Non-Technical Employees Are Bypassing Traditional CI/CD Pipelines(07:30) Injecting Security Context into Agents Using MCP (Model Context Protocol)(10:30) The Anti-Pattern: Abandoning Preventative Cloud Controls for AI Buzzwords(12:20) Identity and Accountability: Why Machines Shouldn't Make Management Decisions(15:30) Why Legacy Pull Requests Are Too Slow for Multi-Agent Workflows(18:20) Moving Security Left: Giving Agents Feedback During Local Execution(22:30) The "Build vs. Buy" Shift: Security Teams Deploying Their Own AI Paved Roads(25:40) Killing the Excel Sheet: Building AI Bots to Explain 403 Errors to Developers(29:00) How to Evaluate AI Workflows Without a Deep Technical Background(32:00) Securing Complex Agent Infrastructure and Maintaining Egress Controls(36:00) Treating AI Agents Like Microservices to Control Sprawl(38:30) Coding Agents vs. Q&A Chatbots: Defining the Threat Model(42:30) Applying Inward Security Policies to the SOC and Threat Hunting Teams

Resources discussed during the interview:

fwd:cloudsec talk - Agentic Paved Roads: Shifting Security Left to the Machine That Thinks