calendar_action
Use the connected Google Calendar account to list and manage events.
This record as markdown: /tools/cowork-os/calendar-action.md
What calendar_action does on CoWork OS
AI agents use calendar_action to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why calendar_action is rated Medium
The tool performs both Read operations (list events) and Write operations (manage events, which typically includes create/update). Since it spans categories and Write is more severe than Read, Write is the appropriate classification. Severity is medium because misuse could create false calendar entries or spam, but the impact is limited to calendar data and can be recovered.
From the tool's definition Tool description states it can 'list and manage events' on a connected Google Calendar account. 'Manage' indicates creation, modification, and potentially deletion of calendar events.
Attacks that exploit this kind of access
The rule that runs calendar_action 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 calendar_action, this is the rule to start with:
calendar_action stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 calendar_action call is checked against it from then on.
Questions about calendar_action
Use the connected Google Calendar account to list and manage events. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for calendar_action: 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.
calendar_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calendar_action 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_action. 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_action 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