Low Risk

getCalendars

getCalendars

How to control getCalendars ↓

What getCalendars does on MCP Apple Calendars

AI agents call getCalendars to retrieve information from MCP Apple Calendars without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getCalendars needs a policy

This tool retrieves calendar data without side effects. Empty descriptions lower confidence slightly, but the naming convention and presence of distinct write/delete operations on the same server strongly indicate getCalendars is a simple read operation with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'getCalendars' indicates a retrieval operation. The description is empty, but the name and context (sibling tools include write/delete operations) clearly suggest this fetches or lists calendar data without modification.

Documented attack patterns abuse exactly the kind of access getCalendars gives an agent:

How to control getCalendars

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Apple Calendars, and nothing reaches the server without passing your rules. This is the rule we recommend for getCalendars:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getCalendars": {}
  }
}

getCalendars is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Apple Calendars — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getCalendars

What does the getCalendars tool do? +

getCalendars. It is categorised as a Read tool in the MCP Apple Calendars MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getCalendars? +

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

What risk level is getCalendars? +

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

Can I rate-limit getCalendars? +

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

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

getCalendars is provided by the MCP Apple Calendars MCP server (shadowfax92/apple-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Apple Calendars tool call.

Start from MCP Apple Calendars, 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 MCP Apple Calendars tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.