Browse calendar events 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_events to load events into the cache first. Ret...
AI agents call browse_events 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.
This tool purely retrieves and queries existing calendar event data from a cache with pagination support. It has no side effects, does not modify or delete data, and does not execute external operations. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' Severity is low because viewing calendar summaries poses minimal risk even if misused by an agent.
From the tool's definition Tool description states it 'Browse calendar events in the cache' and 'Returns summary information' with pagination. No modifications, deletions, or external operations are performed—only retrieval and display of cached calendar data.
Documented attack patterns abuse exactly the kind of access browse_events gives an agent:
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_events:
{
"version": "1",
"default": "deny",
"tools": {
"browse_events": {}
}
}browse_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Browse calendar events 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_events to load events into the cache first. Returns: {current_page: integer, total_pages: integer, count: integer, total_count: integer, events: array, date_range: string, timezone: string}. It is categorised as a Read tool in the Microsoft Graph MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for browse_events: 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.
browse_events 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 browse_events 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 browse_events. 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.
browse_events 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.
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.