listEvents

Lists or searches Google Calendar events. Defaults to the user

SERVERClaude MCP x Google Docs SOURCEa-bonus/google-docs-mcp

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/a-bonus-google-docs-mcp/listevents.md

WHAT IT DOES

What listEvents does on Claude MCP x Google Docs

AI agents call listEvents to retrieve information from Claude MCP x Google Docs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why listEvents is rated Low

The tool retrieves calendar event information (list/search). It does not create, modify, delete, or execute operations. The default behavior of querying the user's calendar is a non-destructive read operation. Severity is low because calendar events are typically low-sensitivity metadata; exposure permits viewing schedules but not altering them or triggering external actions.

From the tool's definition Tool description states 'Lists or searches Google Calendar events' — both list and search operations are query/retrieval functions that return data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listEvents safely

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

listEvents Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP x Google Docs, apply this rule, and every listEvents call is checked against it from then on.

FAQ

Questions about listEvents

What does the listEvents tool do? +

Lists or searches Google Calendar events. Defaults to the user. It is categorised as a Read tool in the Claude MCP x Google Docs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listEvents? +

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

What risk level is listEvents? +

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

Can I rate-limit listEvents? +

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

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

listEvents is provided by the Claude MCP x Google Docs MCP server (a-bonus/google-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude MCP x Google Docs, and thousands of servers like it.

This server

All 84 Claude MCP x Google Docs tools →

Across the catalogue

The MCP Attack Database →

Guides

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