get_email
AI agents call get_email to retrieve information from Zimbra MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_email' and its position among other Zimbra email management tools (create_draft, delete_emails, create_contact) strongly indicate a retrieval operation. There is no evidence of side effects, modifications, or execution. Lower confidence (0.85 vs higher) due to empty description, but the naming convention and sibling tools support a Read classification.
From the tool's definition Tool name 'get_email' and server context describing 'searching, sending, drafting emails' suggests email retrieval. The sibling tools include 'download_attachment' and 'create_draft', indicating this server manages email operations.
Attacks that exploit this kind of access
get_email. It is categorised as a Read tool in the Zimbra MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zimbra MCP Server MCP server in PolicyLayer and add a rule for get_email: 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 Zimbra MCP Server. Nothing to install.
get_email 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 get_email 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 get_email. 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.
get_email is provided by the Zimbra MCP Server MCP server (jeremie-lesage/zimbra-mcp). 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 →