<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agentic-Ai on krash.dev</title><link>https://krash.dev/tags/agentic-ai/</link><description>Recent content in Agentic-Ai on krash.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 08:29:09 +0530</lastBuildDate><atom:link href="https://krash.dev/tags/agentic-ai/rss.xml" rel="self" type="application/rss+xml"/><item><title>Securing MCP Servers: A Threat Modeling Guide for Security Engineers</title><link>https://krash.dev/posts/securing-mcp/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/securing-mcp/</guid><description>&lt;p&gt;Model Context Protocol servers are appearing inside organizations faster than most security teams have a review process for them.&lt;/p&gt;
&lt;p&gt;They often look like small, polite integrations: a package, a few tool definitions, some outbound API calls, and a README.&lt;/p&gt;
&lt;p&gt;That framing is the problem.&lt;/p&gt;
&lt;p&gt;An MCP server is not a passive integration. It is an execution surface exposed to a language model. It may hold credentials, read sensitive data, call internal APIs, write to downstream systems, and act on instructions that came from untrusted text.&lt;/p&gt;</description></item></channel></rss>