Get detailed information for a specific calendar event by its cache number. WORKFLOW: First call browse_events or search_events to get event list, then use this tool with cache number from results. Returns: Event object with id, subject, start, end, location, attendees, body, recurrence, and onli...
AI agents call get_event_detail 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 performs a query operation to fetch calendar event metadata. It has no capability to modify, delete, or execute actions—it only reads and returns event information. The severity is low because exposure of calendar event details, while potentially containing sensitive information, does not enable destructive or financial operations.
From the tool's definition Tool retrieves calendar event details (id, subject, start, end, location, attendees, body, recurrence, online meeting details) without modification.
Documented attack patterns abuse exactly the kind of access get_event_detail 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 get_event_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_event_detail": {}
}
}get_event_detail 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.
Get detailed information for a specific calendar event by its cache number. WORKFLOW: First call browse_events or search_events to get event list, then use this tool with cache number from results. Returns: Event object with id, subject, start, end, location, attendees, body, recurrence, and online meeting details. Note: Invalid cache_number returns appropriate error message. 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 get_event_detail: 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.
get_event_detail 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_event_detail 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_event_detail. 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_event_detail 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.