list_calendar_events

Lists events from the Mac's Calendar app (Calendar.app, local/iCloud calendars) in a date range. Defaults to today + 7 days. For a Microsoft 365 calendar use m365_list_events instead.

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/list-calendar-events.md

WHAT IT DOES

What list_calendar_events does on Local

AI agents call list_calendar_events to retrieve information from Local 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
`limit`	integer	—	Max number of events to return (most recent first within the range). Optional; defaults to all in range.
`calendar`	string	—	Filter by calendar name — partial, case-insensitive match (optional). Use list_calendar_names to see available names.
`end_date`	string	—	ISO 8601 date (YYYY-MM-DD). Defaults to start_date + 7 days.
`start_date`	string	—	ISO 8601 date (YYYY-MM-DD). Defaults to today.
`calendar_id`	string	—	Filter by a single calendar UUID from list_calendar_names (optional).
`calendar_ids`	array	—	Filter by multiple calendar UUIDs (optional).

Parameters from the server's own tool schema.

RISK

Why list_calendar_events is rated Low

This tool only retrieves calendar data within a specified date range from local or iCloud calendars. It has no side effects—it does not create, modify, delete, or execute any operations. Reading calendar events is a low-risk information retrieval action with limited blast radius even if misused by an AI agent, as it only exposes scheduling information that may already be visible to the user.

From the tool's definition Tool name 'list_calendar_events' and description explicitly state it 'Lists events from the Mac's Calendar app' with no modification, deletion, or execution capabilities mentioned. The action is purely retrieval-based.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_calendar_events safely

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

list_calendar_events Allowed

list_calendar_events 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": {
    "list_calendar_events": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every list_calendar_events call is checked against it from then on.

FAQ

Questions about list_calendar_events

What does the list_calendar_events tool do? +

Lists events from the Mac's Calendar app (Calendar.app, local/iCloud calendars) in a date range. Defaults to today + 7 days. For a Microsoft 365 calendar use m365_list_events instead. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

What parameters does list_calendar_events accept? +

list_calendar_events accepts 6 parameters: limit, calendar, end_date, start_date, calendar_id, calendar_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_calendar_events? +

Register the Local MCP server in PolicyLayer and add a rule for list_calendar_events: 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 Local. Nothing to install.

What risk level is list_calendar_events? +

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

Can I rate-limit list_calendar_events? +

Yes. Add a rate_limit block to the list_calendar_events 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 list_calendar_events completely? +

Set action: deny in the PolicyLayer policy for list_calendar_events. 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 list_calendar_events? +

list_calendar_events is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server →get_ctf_calendar on CTFtime MCP Server → The MCP Attack Database →

Guides

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