Manage calendar events where you are an attendee (events organized by others). Actions: accept, decline, tentatively_accept, propose_new_time, delete_cancelled, email_attendees. WORKFLOW: Use cache_number from browse_events or search_events results. Returns: Response confirmation message with act...
AI agents use manage_event_as_attendee to create or update resources in Microsoft Graph MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft Graph MCP Server environment.
The tool modifies calendar state and sends emails, which are Write operations. While some actions like accepting/declining are reversible user-state changes, proposing new times and emailing attendees constitute meaningful modifications. The severity is medium because misuse affects meeting coordination and attendee communications but does not delete data irreversibly or move money.
From the tool's definition Tool enables modifying calendar event responses (accept, decline, tentatively_accept, propose_new_time) and deleting cancelled events (delete_cancelled).
Documented attack patterns abuse exactly the kind of access manage_event_as_attendee 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 manage_event_as_attendee:
{
"version": "1",
"default": "deny",
"tools": {
"manage_event_as_attendee": {
"limits": [
{
"counter": "manage_event_as_attendee_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_event_as_attendee stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage calendar events where you are an attendee (events organized by others). Actions: accept, decline, tentatively_accept, propose_new_time, delete_cancelled, email_attendees. WORKFLOW: Use cache_number from browse_events or search_events results. Returns: Response confirmation message with action status and updated event information. Note: If event is already responded to, returns appropriate error message. IMPORTANT: accept/decline/tentatively_accept/propose_new_time actions will automatically handle events where the organizer didn. It is categorised as a Write tool in the Microsoft Graph MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for manage_event_as_attendee: 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.
manage_event_as_attendee is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_event_as_attendee 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 manage_event_as_attendee. 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.
manage_event_as_attendee 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.