Low Risk

browse_email_cache

Browse emails in the cache with pagination. Returns summary information with number column indicating position in cache. Use page_number to navigate. Automatically manages browsing state with disk cache for persistence. WORKFLOW: Use search_emails to load emails into the cache first. ATTACHMENT I...

How to control browse_email_cache ↓

What browse_email_cache does on Microsoft Graph MCP Server

AI agents call browse_email_cache to retrieve information from Microsoft Graph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why browse_email_cache needs a policy

This tool only queries and retrieves email information from a cache with pagination support. It does not create, modify, delete, or execute operations. The inclusion of attachment metadata (id, name, size, contentType) is informational only. Browsing cached emails with read-only access is a standard data retrieval operation with minimal risk—no side effects, no data modification, no external command execution.

From the tool's definition Tool description states 'Browse emails in the cache with pagination' and 'Returns summary information'. The workflow indicates it retrieves cached email data after search_emails loads them.

Documented attack patterns abuse exactly the kind of access browse_email_cache gives an agent:

How to control browse_email_cache

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

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

browse_email_cache 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 Microsoft Graph MCP Server — 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 browse_email_cache

What does the browse_email_cache tool do? +

Browse emails in the cache with pagination. Returns summary information with number column indicating position in cache. Use page_number to navigate. Automatically manages browsing state with disk cache for persistence. WORKFLOW: Use search_emails to load emails into the cache first. ATTACHMENT INFO: Each email now includes attachment details (id, name, size, contentType) so you can see what attachments are available before downloading. IMAGE ATTACHMENTS: When you see image attachments (contentType starts with. It is categorised as a Read tool in the Microsoft Graph MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_email_cache? +

Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for browse_email_cache: 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 Microsoft Graph MCP Server. Nothing to install.

What risk level is browse_email_cache? +

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

Can I rate-limit browse_email_cache? +

Yes. Add a rate_limit block to the browse_email_cache 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 browse_email_cache completely? +

Set action: deny in the PolicyLayer policy for browse_email_cache. 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 browse_email_cache? +

browse_email_cache is provided by the Microsoft Graph MCP Server MCP server (marlonluo2018/microsoft_graph_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Microsoft Graph MCP Server tool call.

Start from Microsoft Graph MCP Server, 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.

19 Microsoft Graph MCP Server 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.