<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prevent on FindPicked</title><link>https://findpicked.com/tags/prevent/</link><description>Recent content in Prevent on FindPicked</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://findpicked.com/tags/prevent/index.xml" rel="self" type="application/rss+xml"/><item><title>Prevent Prompt Injection in AI Coding Agents</title><link>https://findpicked.com/blog/prevent-prompt-injection-ai-coding-agents/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://findpicked.com/blog/prevent-prompt-injection-ai-coding-agents/</guid><description>&lt;p&gt;AI coding agents are vulnerable to &lt;strong&gt;prompt injection&lt;/strong&gt; because they read and act on untrusted text from repos, docs, issues, search results, RAG stores, and tools that look like instructions. The durable fix is not “better prompting” alone; it is &lt;strong&gt;system design&lt;/strong&gt;: strict permission boundaries, untrusted-data handling, tool allowlists, human review on dangerous actions, and workflows that assume attackers can hide instructions anywhere your agent can read.&lt;/p&gt;
&lt;p&gt;This guide explains how prompt injection reaches coding agents and &lt;strong&gt;MCP-based&lt;/strong&gt; workflows, what failures matter most in practice, and which defensive patterns actually reduce risk over time.&lt;/p&gt;</description></item></channel></rss>