More MLOps.community episodes

Agents Acting Safely on Our Behalf thumbnail

Agents Acting Safely on Our Behalf

Published 15 Oct 2026

Duration: 00:23:05

"Web infrastructure must evolve to support AI agents securely, with protocols like WebMCP enabling safe, deterministic actions while accommodating diverse interaction methods and user control."

Episode Description

What happens to the web when the ones browsing it are no longer people? Sarah Drasner, Area Tech Lead at Google, sits down with us ahead of her Agenti...

Overview

The podcast discusses the evolving relationship between AI agents and the web, focusing on how the web should be adapted to better support agent interactions. Central to this is the Web Machine Client Protocol (WebMCP), which enables developers to define structured, secure actions for agents, reducing risks like prompt injection and ensuring deterministic behavior. By embedding machine-readable instructions and security annotations, the web can become more agent-friendly while maintaining safety, efficiency, and user control.

Various agent interaction models are explored, including in-app browsers, headless automation, co-browsing, and hybrid approaches, emphasizing the need for the web to support diverse modalities. Security is reinforced through mechanisms like origin sets, spending limits, and spotlighting critical data, ensuring agents operate within trusted boundaries. Practical applications include automating repetitive tasks such as gathering logos or photos for design workflows, where AI handles execution but humans retain creative oversight. The discussion also highlights the importance of strategic engineering, cross-team collaboration, and proactive risk assessment - such as using premortems - to build trustworthy, user-centric AI systems that cater to both technical and non-technical users.

What If

  • What if you built a WebMCP gateway to automate client workflows without their developers writing new code?

    • Move: Develop a reverse proxy that injects WebMCP annotations into existing web apps' HTML, enabling AI agents to securely perform actions like form fills, data extraction, and state checks - without requiring changes to the original site.
    • Why Now?: Many businesses rely on legacy or third-party sites that won't adopt WebMCP natively; a gateway lowers adoption barriers and lets solo devs offer automation as a service today.
    • Expected Upside: You can package this as a lightweight SaaS tool for marketers, researchers, or ops teams to automate repetitive site interactions - monetizing secure, deterministic agent access across non-cooperative domains.
  • What if you created a personal agent containment system to safely outsource routine tasks like data collection and file prep?

    • Move: Configure a headless agent with strict origin sets (e.g., only allowed domains), spending limits ($0), and read-only defaults, using WebMCP hints to block unsafe actions - then deploy it to gather logos, speaker images, or public data and auto-upload to Canva or Airtable.
    • Why Now?: With rising demand for content creation and low-code automation, solo developers can offload drudgery while maintaining control over output and security.
    • Expected Upside: Reclaim 5 - 10 hours/week of manual work, reduce errors in asset pipelines, and create reusable templates for clients or side projects.
  • What if you added WebMCP action hints to your own web app to make it agent-first and attract AI-native users?

    • Move: Annotate key user flows (e.g., checkout, form submit, data export) in your app with WebMCP metadata - declaring intent, security context (read/write), and expected outcomes - so AI agents can interact reliably without DOM scraping.
    • Why Now?: Early adopters of agent-friendly protocols will gain visibility in AI-driven search and automation platforms; being first makes your app a default choice for agent-based integrations.
    • Expected Upside: Increase user retention by enabling seamless AI assistance, differentiate from competitors, and open new distribution channels via agent marketplaces or workflow tools.

Takeaway

  • Implement WebMCP in your web applications to expose structured, secure endpoints for AI agents, enabling deterministic interactions and reducing reliance on fragile DOM scraping.
  • Add security annotations (e.g., read-only, user-content exclusion) to your site's interactive elements to mitigate prompt injection risks and control agent behavior.
  • Design agent workflows with origin sets by restricting automated actions to predefined domains or services, especially when handling sensitive tasks like purchases or data transfers.
  • Integrate consequential hints in your UI to trigger user confirmation before high-impact actions (e.g., checkouts, deletions), ensuring safety in hybrid human-agent workflows.
  • Automate repetitive asset-handling tasks (e.g., downloading logos, extracting images) using AI agents while retaining manual control for creative decisions, improving efficiency without sacrificing quality.

Recent Episodes of MLOps.community

29 Oct 2026 From Slop Code to Software Factories

"Tandem biking in Amsterdam's chaotic cycling culture led to a critique of AI-assisted coding's flaws, particularly its tendency to produce unmaintainable, poorly structured code, raising concerns about long-term software reliability."

22 Oct 2026 Token Maxxing Is Over and Here Is What Comes Next

"AI in software development offers benefits but faces challenges like nonsensical outputs and over-reliance; smaller, controlled models like Sonnet improve adoption, while measuring ROI and human-AI collaboration are key to success."

8 Oct 2026 Inside a Game Where AI Agents Never Sleep

"AI integration in gaming, media, and software enhances dynamic gameplay, development efficiency, and user engagement while addressing challenges in balancing difficulty, personalization, and ethical considerations."

More MLOps.community episodes