<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/9cb5cb6d1e604490a0f589e2820cf58c&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9cb5cb6d1e604490a0f589e2820cf58c-fdd7860283475c87.gif</thumbnail_url><duration>182.983</duration><title>Introducing Flint, a Session Firewall for MCP-Connected Agents</title><description>In this video, I discuss the development of Flint, a session firewall designed for MCP-connected agents. Current controls fail to address risks that arise from the sequence of authorized actions, as demonstrated in incidents like the Superbase and Cursor attacks. Flint implements a two-layer system: a role-based access control layer and a behavioral detection layer that tracks data flow across tool calls. I have already built the role-based detection and several behavioral detection rules, and I am currently working on an inline gateway to enhance security. I encourage you to provide feedback on these developments as we move forward.</description></oembed>