AI agents call mail__get_thread to retrieve information from Proton-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing email thread data without creating, modifying, deleting, or executing any external actions. It is a straightforward read operation on email messages. The low severity reflects minimal risk even if misused, as it only exposes already-stored message content to which the authenticated user likely has access.
From the tool's definition Tool name 'mail__get_thread' and description 'Fetch the full email chain (thread) for a message' — the verb 'Fetch' and lack of any modification language indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access mail__get_thread gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for mail__get_thread:
{
"version": "1",
"default": "deny",
"tools": {
"mail__get_thread": {}
}
}mail__get_thread is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch the full email chain (thread) for a message. It is categorised as a Read tool in the Proton-MCP MCP Server, which means it retrieves data without modifying state.
Register the Proton- MCP server in PolicyLayer and add a rule for mail__get_thread: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Proton-MCP. Nothing to install.
mail__get_thread is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mail__get_thread rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for mail__get_thread. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
mail__get_thread is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proton-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.