google-workspace.calendar_event_create
Create a Google Calendar event. Confirm with the user before calling.
This record as markdown: /tools/cowork-os/google-workspace.calendar-event-create.md
What google-workspace.calendar_event_create does on CoWork OS
AI agents use google-workspace.calendar_event_create 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 google-workspace.calendar_event_create is rated Medium
Creating calendar events is a reversible write operation that modifies user data (the calendar). It has medium severity because misuse could spam a user's calendar, block their time, or create confusion, but the impact is limited to scheduling and is easily undoable. It does not destroy data, execute arbitrary code, or move money, so Write is the correct classification rather than Execute or higher categories.
From the tool's definition The tool description explicitly states it "Create[s] a Google Calendar event," which is a data creation operation.
Attacks that exploit this kind of access
The rule that runs google-workspace.calendar_event_create 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_event_create, this is the rule to start with:
google-workspace.calendar_event_create 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 google-workspace.calendar_event_create call is checked against it from then on.
Questions about google-workspace.calendar_event_create
Create a Google Calendar event. Confirm with the user before calling. 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 google-workspace.calendar_event_create: 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_event_create 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 google-workspace.calendar_event_create 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_event_create. 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_event_create 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