Check availability of attendees for a given date. WORKFLOW: Typically use before calling manage_my_event with create action to find optimal meeting times. Automatically includes the organizer (you) in the availability check to ensure overlap-free time slots. Automatically calculates time range ba...
AI agents call check_attendee_availability 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 retrieves calendar availability information for attendees to inform scheduling decisions. It has no side effects—it does not create, modify, delete, or execute actions. The capability to read free/busy status is foundational to Write-category tools like manage_my_event, but the tool itself is purely informational.
From the tool's definition Tool description states it "Check[s] availability of attendees for a given date" and "calculates time range based on all attendees." The workflow explicitly notes it is used "before calling manage_my_event" to find meeting times, indicating it retrieves and…
Documented attack patterns abuse exactly the kind of access check_attendee_availability 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 check_attendee_availability:
{
"version": "1",
"default": "deny",
"tools": {
"check_attendee_availability": {}
}
} check_attendee_availability 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.
Check availability of attendees for a given date. WORKFLOW: Typically use before calling manage_my_event with create action to find optimal meeting times. Automatically includes the organizer (you) in the availability check to ensure overlap-free time slots. Automatically calculates time range based on all attendees. 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 check_attendee_availability: 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.
check_attendee_availability 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 check_attendee_availability 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 check_attendee_availability. 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.
check_attendee_availability 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.