Skip to content

Details

We are excited to bring you an invite to our third event in 2026, this time on Thursday Nov 10, 2026 in partnership with our co-hosts Antler!

Agents now run commands, call tools and touch production. The guardrails around them are supposed to keep them in line, and the logs they write are supposed to tell us what they did. This meetup looks at what happens when neither holds up.

​Talks
​Bypassing Agent-Framework Guardrails: How I Vibe Coded a Scanner to Find 7 Vulnerabilities
Ahmed Khan
Ahmed set out to hunt for bugs in MCP servers. He vibe coded a scanner, mcp-hunt, and ran it across 141 repos. It found no MCP bugs, but it did find one in an agent orchestration framework, which he disclosed and the maintainer patched (CVE pending). He then scanned the 1,000 most-used agent frameworks and MCP servers and came away with 7 vulnerabilities. This is the story behind them.

​A Log Is a Story the Agent Told About Itself: Independently Verifying What AI Agents Did
Lei Zhou
When an agent runs commands on your machine, the agent writes the record of what it did. Signing a log proves nobody altered it, not that it’s true. An action the agent never wrote down leaves nothing to sign. Lei presents anchorstamp, an open-source Rust proof of concept that checks each agent claim against an observer the agent can’t reach: the Linux kernel’s audit subsystem. The live demo covers an honest agent, a forged claim, a hidden action, and an agent trying to tamper with the evidence. Lei will also be clear about what this approach cannot prove.

​What if developers could identify security vulnerabilities before their code even reaches the CI/CD pipeline?
​*Ashvin Ravi* will introduce an AI-powered Security Audit Skill that analyzes source code repositories, identifies potential vulnerabilities, and maps findings to established frameworks such as OWASP Top 10 and MITRE ATT&CK.
​He will also explore how this approach extends to AWS CDK repositories, generating actionable cloud security recommendations and helping developers integrate security earlier into the development lifecycle.

​Agenda
5:30 PM Doors, food and networking
6:00 PM Welcome
6:10 PM Talks + Q&A
7:30 PM Open discussion and networking
8:30 PM Close
​
AISecEng Toronto
​The AI Security Engineers Community (AISecEng) Toronto is a local, practitioner-led chapter dedicated to the emerging field of AI and ML security. It brings together security engineers, researchers, and developers to share practical strategies for securing AI technologies.

Related topics

AI/ML
Artificial Intelligence
Computer Security

Sponsors

Snyk

Snyk

AI Security platform trusted by the world’s most innovative companies

You may also like