AI agents call daily_digest to retrieve information from Mail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and summarizes email data (unread, flagged, and today's messages) without modifying, sending, or deleting anything. It is a read-only aggregation/reporting tool.
From the tool's definition Structured daily overview: unread, flagged, and today's messages
Attacks that exploit this kind of access
Structured daily overview: unread, flagged, and today's messages. It is categorised as a Read tool in the Mail MCP Server, which means it retrieves data without modifying state.
Register the Mail MCP server in PolicyLayer and add a rule for daily_digest: 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 Mail. Nothing to install.
daily_digest 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 daily_digest 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 daily_digest. 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.
daily_digest is provided by the Mail MCP server (kpihx/mail-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 →