Check calendar availability for scheduling
AI agents call check_availability to retrieve information from Microsoft MCP 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 to inform scheduling decisions. It does not create, modify, delete, or execute operations—it only reads calendar data. The blast radius of misuse is minimal (unauthorized viewing of calendar information), making it a Read category tool with low severity.
From the tool's definition Tool is described as checking calendar availability for scheduling, which is a query operation that retrieves calendar data without modifying anything. The verb 'check' indicates passive information retrieval rather than side effects.
Attacks that exploit this kind of access
Check calendar availability for scheduling. It is categorised as a Read tool in the Microsoft MCP MCP Server, which means it retrieves data without modifying state.
Register the Microsoft MCP server in PolicyLayer and add a rule for check_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 MCP. Nothing to install.
check_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_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_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_availability is provided by the Microsoft MCP server (purva-kashyap/microsoft-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →