list-events

List calendar events. Returns: array of event objects with id, summary, start, end, status, recurrence. Use when: viewing schedule, finding events. Note: supports batch (up to 50 calendars).

SERVERMCP Google Workspace SOURCE199-mcp/mcp-google

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/199-biotechnologies-mcp-google/list-events.md

WHAT IT DOES

What list-events does on MCP Google Workspace

AI agents call list-events to retrieve information from MCP Google Workspace 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-events is rated Low

This tool retrieves and queries calendar event data with no side effects. It is a pure read operation that returns event metadata (id, summary, start, end, status, recurrence). While it operates within the Google Workspace ecosystem which has delete and financial capabilities elsewhere, this specific tool only lists/views data.

From the tool's definition Tool name is 'list-events' and description states 'List calendar events. Returns: array of event objects' with use cases 'viewing schedule, finding events'. No modification, deletion, or execution occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list-events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-events, this is the rule to start with:

list-events Allowed

list-events 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-events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every list-events call is checked against it from then on.

FAQ

Questions about list-events

What does the list-events tool do? +

List calendar events. Returns: array of event objects with id, summary, start, end, status, recurrence. Use when: viewing schedule, finding events. Note: supports batch (up to 50 calendars). It is categorised as a Read tool in the MCP Google Workspace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-events? +

Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for 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 MCP Google Workspace. Nothing to install.

What risk level is list-events? +

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

Can I rate-limit list-events? +

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

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

list-events is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Google Workspace, and thousands of servers like it.

This server

All 26 MCP Google Workspace tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →