<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Thiago Avelino</title><link>https://avelino.run/tags/security/</link><description>Recent content in Security on Thiago Avelino</description><generator>Hugo</generator><language>en-us</language><copyright>© Avelino</copyright><lastBuildDate>Mon, 06 Apr 2026 18:12:41 -0300</lastBuildDate><atom:link href="https://avelino.run/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>The governance problem MCP created without asking</title><link>https://avelino.run/mcp-governance-token-sprawl/</link><pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate><guid>https://avelino.run/mcp-governance-token-sprawl/</guid><description>&lt;p>My team adopted MCP fast. I encouraged it — the productivity gains were real and visible. Engineers connecting Sentry, Slack, Grafana, GitHub directly into their workflow, no friction. The kind of thing you want to happen organically.&lt;/p>
&lt;p>Then one day I asked a simple question: who has a Sentry token? Who has Slack? Grafana?&lt;/p>
&lt;p>The answer was: everyone. Each engineer had generated their own. No inventory. No rotation policy. No single revocation point. We had traded operational security for developer experience — and nobody had made that trade explicitly. It just happened, one &lt;code>mcp add&lt;/code> at a time.&lt;/p></description></item></channel></rss>