Disconnect from an email account.
AI agents call imap_disconnect as a supporting operation in Email MCP Server workflows.
This tool terminates a connection to an email server. It does not read, write, execute, delete data, or involve financial transactions. It is a session/connection management operation with minimal blast radius — at worst it interrupts an active session, which is reversible by reconnecting.
From the tool's definition Disconnect from an email account.
Attacks that exploit this kind of access
Disconnect from an email account. It is categorised as a Other tool in the Email MCP Server MCP Server, which means it performs auxiliary operations.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_disconnect: 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 Email MCP Server. Nothing to install.
imap_disconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the imap_disconnect 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 imap_disconnect. 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.
imap_disconnect is provided by the Email MCP Server MCP server (sventern/mcp_email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →