The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/AI & Data/Securing the Realm
Securing the Realm artwork

MVP Summit - Quickfire Questions with one half of Copilot Connection!

Securing the Realm · 2026-03-30 · 10 min

0:00--:--

Key moments - from our scoring

Substance score

46 / 100

Five dimensions, 20 points each

Insight Density9 / 20
Originality10 / 20
Guest Caliber12 / 20
Specificity & Evidence7 / 20
Conversational Craft8 / 20

Kevin McDonald explores how AI is evolving from a developer-centric technology to something accessible to broader audiences through intuitive skill-building and extensibility frameworks like Model Context Protocol (MCP). He highlights real-world examples including GitHub's use of coding agents with skills in VS Code and Microsoft's ambient AI initiatives like meeting facilitators in Teams and channel agents, drawing a parallel to dungeon master AI in collaborative environments. The conversation pivots to the dual challenge of securing AI systems (protection via firewalls and barriers) versus governing them (determining appropriate use cases and ethical boundaries). McDonald emphasizes that governance isn't purely rule-based but involves continuous evaluation and red-teaming - techniques he explored with Chris Huntingford and Zoe Wilson at ESPC Dublin. He references Foundry Evaluations as a tool for continuous assessment across different models, while acknowledging personal skepticism about ambient capabilities like always-listening agents. The discussion touches on acceptance factors and the need to challenge whether new AI capabilities are genuinely beneficial, drawing insights from his wife's critical AI perspective as a grounding mechanism.

Key takeaways

  • →AI's evolution toward skills-based development is democratizing agent creation beyond traditional developers, making agentic capabilities accessible to non-technical users.
  • →Ambient AI - agents integrated into natural workflows like Teams meetings or home environments - represents the next phase, but requires careful governance on when and where these systems should participate.
  • →Security and governance are distinct challenges: security prevents unauthorized access while governance defines ethical boundaries and appropriate use cases through continuous evaluation and red-teaming.
  • →Foundry Evaluations enables continuous red-teaming and model comparison to define and test guardrails, functioning as a CI/CD pipeline for AI safety.
  • →Personal skepticism and critical questioning about AI capabilities' real-world value is essential to prevent overdeployment of technology for its own sake.

Guests

Kevin McDonald

Topics in this episode

ClaudeModel Context Protocol (MCP)Copilot Studiored teamingVS CodeCopilot Connection podcastGitHub coding agentsMicrosoft Teams meeting facilitatorsOpenClawsFoundry Evaluations

Questions this episode answers

What is the Model Context Protocol (MCP) and how does it relate to AI democratization?

MCP is one of several protocols opening up AI extensibility to more people, enabling natural skill-writing capabilities that allow non-developers to build agent functionality without deep technical knowledge.

How does ambient AI differ from traditional chatbot interactions?

Ambient AI runs continuously in the background of applications like Teams meetings or smart home devices, listening and suggesting without being explicitly triggered, versus requiring active user initiation like traditional chatbots.

What's the difference between security and governance for AI systems?

Security protects systems from unauthorized access through firewalls and barriers throughout the architecture, while governance defines what AI should and shouldn't do ethically, determining appropriate use cases and ethical boundaries.

How can organizations use Foundry Evaluations for AI safety?

Foundry Evaluations enables continuous red-teaming and performance comparison across different models to define guardrails, test AI behavior against intended boundaries, and assess whether systems perform safely in various scenarios.

What examples does Kevin McDonald give of ambient AI in practice?

Meeting facilitators in Teams that capture context and nudge participants, GitHub's coding agents with skills in VS Code, and smart home devices like Alexa that could hypothetically join conversations to offer suggestions.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

9 / 20

The episode contains some legitimate technical observations about AI skill democratization, ambient computing, and the distinction between security and governance - but these insights are scattered amid considerable rambling, incomplete thoughts, and filler. Kevin's points about MCP protocols, agent architecture, and red-teaming have substance, but are surrounded by tangential anecdotes (Alexa in kitchen, wife's skepticism, isolated Mac mini setup) that dilute density. For a 10-minute quickfire, the signal-to-noise ratio is below average for a B2B conversation.

the ability to write skills is a very natural thing for people
there's two different questions there. Yes. intentionally that they're put together, but there's two different stories. There's one protecting it of making sure absolutely

Originality

10 / 20

The guest rehearses familiar macro trends (democratization of AI, ambient computing, ubiquity) and references well-circulated figures (Jamie Teevan, Peter Steinberger, Scott Hanselman) without sharp differentiation. The distinction between security and governance is useful but briefly sketched. Most of the framing - skills lowering barriers, AI moving from personal to ambient - is already circulating in mainstream AI discourse. No genuinely counterintuitive or first-principles thinking emerges.

we're going to see it open up to more people
we're going to see more things where it happens, channel agents in teams, things that sit there while you're doing stuff

Guest Caliber

12 / 20

Kevin McDonald is a relevant practitioner: co-host of Copilot Connection, works with Avanade on Copilot extensibility, has hands-on exposure to Copilot Studio, and has run workshops (ESPC Dublin) on red-teaming and evaluations. He is not a CEO or operator at scale, nor is he a pure researcher - he sits in the practitioner/developer ecosystem. His credibility is solid for a technical episode but not exceptional for a B2B business context. No seat-of-the-pants entrepreneurial or revenue-facing perspective emerges.

I'm the co host of the Copilot Connection podcast, ⁓ Microsoft and Copilot and Copilot extensibility
we did a workshop at ESPC in Dublin with Chris Huntingford and Zoe Wilson

Specificity & Evidence

7 / 20

The episode is severely lacking in concrete data, metrics, timelines, and named examples. Kevin alludes to protocols (MCP, A2A), tools (GitHub Copilot, VS Code, Foundry Evaluations, OpenClaw), and names (Jamie Teevan, Peter Steinberger, Gary Trinder, Scott Hanselman), but provides almost no specific numbers, case studies, real-world deployment examples, or measurable outcomes. The workshop at ESPC is mentioned but not detailed. Red-teaming and evaluations are discussed without concrete results or examples. This is abstract pontification masked as discussion.

she was doing with her coding agents with skills ⁓ running in VS code
we did a workshop at ESPC in Dublin with Chris Huntingford and Zoe Wilson

Conversational Craft

8 / 20

The host asks some reasonable setup questions ('Where do you see AI going?', 'How do we secure this stuff?') but rarely follows up with depth or pushback. When Kevin tangles or loses his thread (e.g., the incomplete thought about OpenClaw structure names), the host does not press for clarity. The host does pivot to Foundry Evaluations and attempts a CI/CD analogy, showing some engagement, but the overall conversation reads as a soft, permissive interview. No genuine disagreement or challenging questions surface; the dynamic is deferential.

skills gap and it's being addressed with skills in the literal sense
Have you tried using something like Foundry Evaluations for that?

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

speaker18interesting7conversation6different6skills5open5side4copilot4world4fascinating4listening4point4evaluations4kevin3microsoft3love3

Episode notes

The conversation delves into the future of AI, discussing its accessibility, the concept of ambient computing, and the ethical governance of AI. Kevin McDonnell shares his insights and a one of his own take aways from the app that started the series!

Full transcript

10 min

Transcribed and scored by The B2B Podcast Index.

speaker-1: So welcome to a quick fire round for securing the realm this week. ⁓ Got a special guest with us usual ⁓ so Kevin, want to just kind of introduce yourself, tell us a about you and we'll kind of get straight into the questions. speaker-0: And it's very funny being this side. So Kevin McDonald.

I'm the co host of the Copilot Connection podcast, ⁓ Microsoft and Copilot and Copilot extensibility. And I'm lucky I get to work with Josh Avanade as well. ⁓ speaker-1: Absolutely. Pleasure, of course.

⁓ No, it's really interesting to have this conversation because ⁓ from my side, looking at Foundry and then you've bringing the Copal extensibility. So you've got both sides of the coin really from a Microsoft AI standpoint. So let's start big. Where do you see AI going?

What's your hot take for the year? speaker-0: I'm fascinated where the kind of skill side, a lot of the things that's happening with Claude, co-work and things, is opening up AI to more and more people. rather, you know, love the MCP, I love, you know, you've got A2A, all these lovely protocols, but the average person is going to go, yeah, I have no idea about this. But I think that ability to write skills is a very natural thing for people.

And I think this evolution that we're seeing of people being able to make more of that is going to start flexing more out of the developers, more out the dev world, and obviously coming from the copilot studio world, it's kind of opening up to lots of people. But I think this will see that transition. And I think that's going to be the fascinating part to it as well. So there's speaker-1: skills gap and it's being addressed with skills in the literal sense.

speaker-0: And I think it's just going to be fascinating to see where people get with it. And we do a co-pilot far side chats every month. We had a poor Yoho from GitHub and the thing she was talking about, you know, I was expecting it to get quite technical, but she wasn't talking about all the things like generating spreadsheets and work on that, that she was doing with her coding agents with skills ⁓ running in VS code. I was looking at going with a little bit of an interface change, anyone could be doing this.

This is that kind of world just with a bit of thinking. I think so we're going back to the original question, where do I think AI is going to go? I think we're going to see it open up to more people of thinking of things that they can do that's a bit different. So I'm really fascinated with that.

And I think the other slight world, and I don't quite know how, ⁓ exactly. But, ⁓ Jamie Teevan, who's the chief scientist at Microsoft has been talking a lot about the we of AI. And I think right now we, it's kind of a personal thing. You go and chat to an agent, use co-pilot, you write some code or it's built into an app, but more and more things like facilitator that that's there in teams that sits there within the meeting, kind of nudging you onto the right thing, listening to what you're doing, capturing that.

we're going to see more things where it happens, channel agents in teams, things that sit there while you're doing stuff. I think, yeah, I look at the Alexa I have, sorry if that's triggered anyone's around there. I look at that, we have one in the kitchen and a number of times when we're kind of eating with the family and someone's got a question, we'll ask that. Now, I'm going to terrify people slightly, but imagine that could join a conversation.

We could have an agent running during this conversation, listening to us. trying to suggest things, open things up. There's going to be a way that that's not intrusive. It knows when to join in.

You don't have to actively trigger it. But I think we will see that evolution as well. It'll really interesting. speaker-1: So kind of an ubiquitousness to it all, if that's the right word.

Ambient computing. speaker-0: Yeah, I think we'll be fine. In fact, if I think of your Dungeons and Dragons one, I actually saw the photo from your first securing the realm at Scottish summit to be able to the thought of having like a dungeon master that sits there with you. That was kind of the first steps we're seeing in that we bringing into the conversation, I think we'll see more and more things.

And I think we'll also see things we haven't thought of before. And that's the bit that some more go. we could use AI for this or we could bring that into the conversation. I always love those moments on there.

I think the technology is there. It's our habits and actually thinking of it that will be the big thing. speaker-1: Yeah, I think I was watching a podcast, Hanselman, it's Scott Hanselman, of course, where he interviewed Peter Steinberger, founder and creator of OpenClaw. Not something I personally use, but one of the things that kind of he kind of said about it was he just put it together.

people hadn't put it together yet. And so, like you said, the technology is there, but it's what we then figure out to do with it next. Yeah, this point. speaker-0: Absolutely.

it was funny when OpenClaw first came out, Gary Trinder was telling me about it. But it was actually the way they were kind of structuring, I can't remember what the different parts of it called, but basically the skills within the main agent itself. He was showing me how to structure that. And I was like, wow, this is just a way of thinking.

I have like a vision one. There was another name for it, I completely forgotten, but the way it kind of brought the different things through. really made sense from there. the kind of back into it was as fascinating as the ability to use it.

And I'm saying to you, haven't set out. Why? Because I'm terrified of what it can do. I don't feel I know enough about it to control it on there.

So at some point, I will might kind of run it in some isolated way with this little, I'm thinking about sort of all this, I know everyone's been buying the Mac minis, been thinking about getting something that's a brand new one. doesn't have anything turned on. Yeah. It's just used for that.

So we kind of have a little bit more control over it. But I think the guard rails for that are going to be fascinating. speaker-1: And moving on to that actually, like, how do we secure this stuff? How do we govern it?

speaker-0: Yeah. And I think there's two different questions there. Yes. intentionally that they're put together, but there's two different stories.

There's one protecting it of making sure absolutely, I was going to say the barriers. know that security is always talking about not having the firewalls, not just protecting the outside, but throughout, but it's that absolute, must not do this. But then there's also the governance. What should it do?

What shouldn't it be doing? How do you kind of keep it on track? And how, how do you kind of look at what it's what is right and what is wrong? And that's a horrible way of saying it, but the kind of ethics of these things, at what point should you allowed to like, for example, do I want my open core to be listening into my dinner conversation and being helpful there?

At what point do you say, no, it shouldn't be listening to that? because we could be discussing sensitive things that we don't want to go out there and we don't, we don't want to be influenced by that. So I think the governance within there is less of strict rules, but more of how do you decide when to use it? How do you stop it from stepping in in those situations?

It's, it's going to be interesting. And I, you know, my wife is, doing AI myself a lot, she's an absolute hater of AI. She just doesn't trust any of the things on that. kind get her, but they get exactly where she's going.

And it grounds me a little bit and kind of, I have in my head, what would Celia do? What would her opinion if I was telling people about this? And I know that open clawed absolutely terrified. If I let her know, she wouldn't let me turn it on at all.

So, it's kind of getting that acceptance factor working out. I think we all need to challenge and say, is this actually a good idea? And I kind of feel we've at times gone too far and stopped. stop checking on is this good idea enough.

speaker-1: You've brought me on to an interesting question actually around, you know, looking at this governance aspect. Have you tried using something like Foundry Evaluations for that? Kind of not necessarily for open call-opix, you're not using it, but yeah, know, the use of the tool. ⁓ speaker-0: A little bit.

Yes, certainly. ⁓ I'm wearing my Jen to get in top we did a workshop at ESPC in Dublin with Chris Huntingford and Zoe Wilson. And that was one the things we were talking about red teaming within that how do you how do you try and get agents to do things they shouldn't do but also you know, what is the barriers you want for that and then using evaluations to run that on a continuous basis, look at it from different models, how does it perform from that? So yes, to a degree, I can always see feel my brain ticking over.

Yeah, this is interesting that I've kind of always done some of those evaluations to define the borders. So I want to make sure it doesn't do this. How far does it get within that? That's interesting to see how much it does do, know, what sort of things come back that come from there as well.

That would be interesting to look at. speaker-1: So kind of like a CI, CD and CE for continuous evaluations. speaker-0: I'm ⁓ speaker-1: We have a tongue twister as well at speed. It's been a real pleasure, Kevin.

Thank you so much for coming on. Cheers. speaker-0: Thank you very much.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • #291 Why Most AI Projects Fail to Deliver ROI, Sinohe Terrero, CFO and COO, EnvoyGrowCFO Show · on Claude91 / 100
  • Why a $1.2B exit felt like his biggest failure, and the customer-obsession thesis behind AgencyThe GTMnow Podcast · on Claude86 / 100
  • Is Your Business Invisible to AI Search? (And How to Fix It) ft. Ray YoungRevenue Science · on Claude85 / 100
  • Episode 018: Season 2, the $75 Consult and the Frankenstein StackAI Tools for Practicing Lawyers · on Claude84 / 100
  • Late checkouts, AI agents and the future of guest communication with Cole Rubin of ConduitMatt Talks Hospitality: Real conversations for innovative hoteliers · on Model Context Protocol (MCP)83 / 100
  • Agentic Engineering for Testers: How to Automate Your Way to the Top with Amit RawatTestGuild Automation Podcast · on Claude82 / 100

More from Securing the Realm

All episodes →
  • AI Operationalisation67 / 100
  • MVP Summit - Agentic Security Roundup87 / 100
  • The Elf Foundry - Vibe Engineering, from Agentic AI to Platform AI
  • The Architecture of AI Transformation
  • Deepfakes, AI Fraud, and authenticity
Explore the best B2B AI & Data podcasts →
All Securing the Realm episodes →