imap_add_account
AI agents use imap_add_account to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
Adding an account creates a new configuration entry that persists and can be used for subsequent email operations. This is a reversible Write operation (accounts can be removed), but with high severity because it involves storing email credentials and establishing access to external email providers.
From the tool's definition Tool name 'imap_add_account' indicates account creation/registration. Server description states it 'enables users to read, search, and send emails across multiple accounts and providers' with 'secure AES-256 encryption', implying credential storage and…
Attacks that exploit this kind of access
imap_add_account. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_add_account: 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_add_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the imap_add_account 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_add_account. 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_add_account 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 →