Check the response status of meeting attendees
AI agents call get_attendee_status to retrieve information from Outlook Calendar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves attendee response statuses (accepted/declined/tentative/no response) from existing calendar events. It is a read-only query operation that has no capability to modify calendar data, execute code, delete information, or trigger financial transactions. The low severity reflects minimal blast radius—misuse would only expose information that the user has authorized access to.
From the tool's definition Tool name 'get_attendee_status' and description 'Check the response status of meeting attendees' indicate querying attendee information with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access get_attendee_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook Calendar MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_attendee_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_attendee_status": {}
}
}get_attendee_status 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 the response status of meeting attendees. It is categorised as a Read tool in the Outlook Calendar MCP MCP Server, which means it retrieves data without modifying state.
Register the Outlook Calendar MCP server in PolicyLayer and add a rule for get_attendee_status: 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 Outlook Calendar MCP. Nothing to install.
get_attendee_status 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_attendee_status 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_attendee_status. 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_attendee_status is provided by the Outlook Calendar MCP server (merajmehrabi/outlook_calendar_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Outlook Calendar MCP, 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.
7 Outlook Calendar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.