calendar_list_events
List upcoming calendar events
This record as markdown: /tools/io-github-alifanov-scopegate/calendar-list-events.md
What calendar_list_events does on ScopeGate
AI agents call calendar_list_events to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why calendar_list_events is rated Low
This tool queries calendar data to retrieve a list of events. It performs a read-only operation with no side effects, no data modification, and no destructive capability. The blast radius of misuse is minimal—an agent could view event details it shouldn't access, but cannot alter, delete, or act upon them.
From the tool's definition Tool name 'calendar_list_events' and description 'List upcoming calendar events' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs calendar_list_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar_list_events, this is the rule to start with:
calendar_list_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every calendar_list_events call is checked against it from then on.
Questions about calendar_list_events
List upcoming calendar events. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate 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 ScopeGate. Nothing to install.
calendar_list_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
calendar_list_events is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue