Low Risk

mail.unread_summary

Get unread email summary across all accounts: unread count per account and recent unread message subjects/senders. Requires Mail.app to be running.

How to control mail.unread_summary ↓

What mail.unread_summary does on Orchard

AI agents call mail.unread_summary to retrieve information from Orchard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why mail.unread_summary needs a policy

This tool retrieves and queries unread email metadata (count, subjects, senders) without creating, modifying, deleting, or executing any operations. It is a read-only operation with no side effects, fitting the Read category with low severity due to limited scope and no destructive potential.

From the tool's definition Tool name 'mail.unread_summary' and description 'Get unread email summary' indicate data retrieval only. No modification, deletion, or execution capabilities are mentioned.

Documented attack patterns abuse exactly the kind of access mail.unread_summary gives an agent:

How to control mail.unread_summary

PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for mail.unread_summary:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail.unread_summary": {}
  }
}

mail.unread_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Orchard — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mail.unread_summary

What does the mail.unread_summary tool do? +

Get unread email summary across all accounts: unread count per account and recent unread message subjects/senders. Requires Mail.app to be running. It is categorised as a Read tool in the Orchard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mail.unread_summary? +

Register the Orchard MCP server in PolicyLayer and add a rule for mail.unread_summary: 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 Orchard. Nothing to install.

What risk level is mail.unread_summary? +

mail.unread_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mail.unread_summary? +

Yes. Add a rate_limit block to the mail.unread_summary 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.

How do I block mail.unread_summary completely? +

Set action: deny in the PolicyLayer policy for mail.unread_summary. 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.

What MCP server provides mail.unread_summary? +

mail.unread_summary is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orchard tool call.

Start from Orchard, 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.

65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.