get-calendar-event

SERVERMs 365 SOURCE@jo3zik/ms-365-mcp-server

Low RISK CLASS

Category Read

Parameters 81 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jo3zik-ms-365-mcp-server/get-calendar-event.md

WHAT IT DOES

What get-calendar-event does on Ms 365

AI agents call get-calendar-event to retrieve information from Ms 365 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`expand`	array	—	Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as
`select`	string	—	Comma-separated fields to return, e.g. id,subject,from,receivedDateTime
`eventId`	string	Yes	Value for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph.
`timezone`	string	—	IANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
`fetchAllPages`	boolean	—	Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a sma
`includeHeaders`	boolean	—	Include response headers (including ETag) in the response metadata
`excludeResponse`	boolean	—	Exclude the full response body and only return success or failure indication
`expandExtendedProperties`	boolean	—	When true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.

Parameters from the server's own tool schema.

RISK

Why get-calendar-event is rated Low

Even though get-calendar-event only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-calendar-event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-calendar-event, this is the rule to start with:

get-calendar-event Allowed

get-calendar-event is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-calendar-event": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every get-calendar-event call is checked against it from then on.

FAQ

Questions about get-calendar-event

What does the get-calendar-event tool do? +

Get the properties and relationships of the specified event object. Currently, this operation returns event bodies in only HTML format. There are two scenarios where an app can get an event in another user's calendar: Since the event resource supports extensions, you can also use the GET operation to get custom properties and extension data in an event instance. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.

What parameters does get-calendar-event accept? +

get-calendar-event accepts 8 parameters: expand, select, eventId, timezone, fetchAllPages, includeHeaders, excludeResponse, expandExtendedProperties. Required: eventId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get-calendar-event? +

Register the Ms 365 MCP server in PolicyLayer and add a rule for get-calendar-event: 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 Ms 365. Nothing to install.

What risk level is get-calendar-event? +

get-calendar-event is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-calendar-event? +

Yes. Add a rate_limit block to the get-calendar-event 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.

How do I block get-calendar-event completely? +

Set action: deny in the PolicyLayer policy for get-calendar-event. 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.

What MCP server provides get-calendar-event? +

get-calendar-event is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ms 365, and thousands of servers like it.

This server

All 194 Ms 365 tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →