Low Risk

calendar.list_events

List events within a time range.

How to control calendar.list_events ↓

What calendar.list_events does on Nucleus Apple

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

Low Risk

Why calendar.list_events needs a policy

This tool retrieves calendar event data without side effects. It queries existing events within a specified time window, matching the definition of a Read operation. The severity is low because listing calendar events poses minimal risk—the data retrieved is typically user's own calendar information without destructive consequences. Confidence is high due to clear, unambiguous naming and description.

From the tool's definition Tool name 'list_events' and description 'List events within a time range' indicate data retrieval with no modification, deletion, or code execution.

Documented attack patterns abuse exactly the kind of access calendar.list_events gives an agent:

How to control calendar.list_events

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

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

calendar.list_events 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 Nucleus Apple — 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 calendar.list_events

What does the calendar.list_events tool do? +

List events within a time range. It is categorised as a Read tool in the Nucleus Apple MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar.list_events? +

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

What risk level is calendar.list_events? +

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

Can I rate-limit calendar.list_events? +

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

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

calendar.list_events is provided by the Nucleus Apple MCP server (zish-rob-crur/nucleus-apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nucleus Apple tool call.

Start from Nucleus Apple, 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.

30 Nucleus Apple 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.