google-workspace.calendar_events_batch_get
Get multiple Google Calendar events by ID from one calendar
This record as markdown: /tools/cowork-os/google-workspace.calendar-events-batch-get.md
What google-workspace.calendar_events_batch_get does on CoWork OS
AI agents call google-workspace.calendar_events_batch_get to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google-workspace.calendar_events_batch_get is rated Low
This tool retrieves calendar event data by querying existing events. It performs no modification, deletion, or side effects on the data. It is a straightforward read operation that queries and returns calendar information. The blast radius of misuse is minimal - an agent could only access calendar event details it has permission to view, with no ability to modify, delete, or trigger actions based on those events.
From the tool's definition Tool description states 'Get multiple Google Calendar events by ID from one calendar' - uses 'Get' which indicates retrieval without modification.
Attacks that exploit this kind of access
The rule that runs google-workspace.calendar_events_batch_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.calendar_events_batch_get, this is the rule to start with:
google-workspace.calendar_events_batch_get 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 CoWork OS, apply this rule, and every google-workspace.calendar_events_batch_get call is checked against it from then on.
Questions about google-workspace.calendar_events_batch_get
Get multiple Google Calendar events by ID from one calendar. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.calendar_events_batch_get: 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 CoWork OS. Nothing to install.
google-workspace.calendar_events_batch_get 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 google-workspace.calendar_events_batch_get 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 google-workspace.calendar_events_batch_get. 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.
google-workspace.calendar_events_batch_get is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue