Low Risk

calendar__list_events

List calendar events in a date range. Can read both Jorgenclaw and Scott calendars.

How to control calendar__list_events ↓

What calendar__list_events does on Proton-MCP

AI agents call calendar__list_events to retrieve information from Proton-MCP 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 within a date range without creating, modifying, deleting, or executing any operations. It is a passive query operation with no side effects, fitting the Read category definition. Severity is low because calendar metadata exposure has limited immediate impact compared to financial or destructive operations.

From the tool's definition Tool name contains 'list' and description explicitly states 'List calendar events' with no modification or deletion capability mentioned. The phrase 'Can read both Jorgenclaw and Scott calendars' confirms retrieval-only intent.

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 Proton-MCP, 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 Proton-MCP — 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 calendar events in a date range. Can read both Jorgenclaw and Scott calendars. It is categorised as a Read tool in the Proton-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar__list_events? +

Register the Proton- 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 Proton-MCP. 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 Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proton-MCP tool call.

Start from Proton-MCP, 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.

36 Proton-MCP 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.