<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Owasp on AegisGate — Secure Every AI Interaction</title><link>https://aegisgatesecurity.io/tags/owasp/</link><description>Recent content in Owasp on AegisGate — Secure Every AI Interaction</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aegisgatesecurity.io/tags/owasp/feed.xml" rel="self" type="application/rss+xml"/><item><title>MCP Tool Poisoning: The Attack Hidden in Plain Text</title><link>https://aegisgatesecurity.io/blog/mcp-tool-poisoning-the-attack-hidden-in-plain-text/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://aegisgatesecurity.io/blog/mcp-tool-poisoning-the-attack-hidden-in-plain-text/</guid><description>In April 2025, Invariant Labs demonstrated something unsettling: you don&amp;rsquo;t need to hack an AI agent to make it misbehave. You just need to describe a tool.
They called it tool poisoning — hidden instructions embedded in MCP tool descriptions that manipulate agent behavior. No authentication bypass. No exploit. Just text in a JSON field that the agent reads as context.
The MCP spec assumes tool metadata is trustworthy. It isn&amp;rsquo;t.</description></item></channel></rss>