<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MCP on mhbxyz.me</title><link>https://mhbxyz.github.io/en/tags/mcp/</link><description>Recent content in MCP on mhbxyz.me</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mhbxyz.github.io/en/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>protonmail-mcp: give an agent email access without a blank check</title><link>https://mhbxyz.github.io/en/articles/protonmail-mcp-give-an-agent-email-access-with-limits/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://mhbxyz.github.io/en/articles/protonmail-mcp-give-an-agent-email-access-with-limits/</guid><description>&lt;h2 id="an-email-is-untrusted-input"&gt;An email is untrusted input&lt;/h2&gt;
&lt;p&gt;Asking an agent to summarize your messages is useful. But other people wrote those messages. A sender can place instructions in one, telling the agent to send data elsewhere, delete a message, or ignore the original request. Giving the agent unrestricted mailbox access can turn a reading task into a risk of unintended action.&lt;/p&gt;
&lt;p&gt;I built &lt;a href="https://github.com/mhbxyz/protonmail-mcp"&gt;protonmail-mcp&lt;/a&gt; around this boundary. The server connects an MCP client to Proton Mail through Proton Bridge, which exposes IMAP and SMTP locally. It offers specific tools to the agent instead of allowing arbitrary IMAP or SMTP commands.&lt;/p&gt;</description></item></channel></rss>