Low Risk

calendar_get_events

Retrieves calendar events from the user\

How to control calendar_get_events ↓

What calendar_get_events does on MCP Google Workspace Server

AI agents call calendar_get_events to retrieve information from MCP Google Workspace Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why calendar_get_events needs a policy

This tool performs a read-only query of calendar data. It retrieves existing events without creating, modifying, or deleting anything. The retrieval of calendar events poses minimal security risk as it only exposes already-existing data the user has access to.

From the tool's definition Tool name is 'calendar_get_events' and description states it 'Retrieves calendar events from the user' — purely a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access calendar_get_events gives an agent:

How to control calendar_get_events

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Workspace Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_get_events:

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

calendar_get_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 MCP Google Workspace Server — 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_get_events

What does the calendar_get_events tool do? +

Retrieves calendar events from the user\. It is categorised as a Read tool in the MCP Google Workspace Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar_get_events? +

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

What risk level is calendar_get_events? +

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

Can I rate-limit calendar_get_events? +

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

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

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

Enforce policy on every MCP Google Workspace Server tool call.

Start from MCP Google Workspace Server, 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.

16 MCP Google Workspace Server 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.