list_calendar_names

Lists the calendars in the Mac's Calendar app (Calendar.app, local/iCloud). For Microsoft 365 calendars use the m365 calendar tools instead.

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 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-names.md

WHAT IT DOES

What list_calendar_names does on Local

AI agents call list_calendar_names 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.

RISK

Why list_calendar_names is rated Low

This tool retrieves calendar metadata (names of calendars) from the local Mac Calendar app without modifying, executing operations, or destroying data. It is a straightforward query operation with minimal risk, even in a multi-calendar environment, as listing calendars does not expose sensitive event data and cannot be misused to cause harm.

From the tool's definition Tool name 'list_calendar_names' and description 'Lists the calendars' indicates a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_calendar_names 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_names, this is the rule to start with:

list_calendar_names Allowed

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

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_names call is checked against it from then on.

FAQ

Questions about list_calendar_names

What does the list_calendar_names tool do? +

Lists the calendars in the Mac's Calendar app (Calendar.app, local/iCloud). For Microsoft 365 calendars use the m365 calendar tools instead. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_calendar_names? +

Register the Local MCP server in PolicyLayer and add a rule for list_calendar_names: 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_names? +

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

Can I rate-limit list_calendar_names? +

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

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

list_calendar_names 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 →