create-event
Create calendar event. Returns: created event with id, htmlLink, start, end, status. Use when: scheduling new appointments/meetings. Note: supports recurring events via recurrence.
This record as markdown: /tools/199-biotechnologies-mcp-google/create-event.md
What create-event does on MCP Google Workspace
AI agents use create-event to create or update resources in MCP Google Workspace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace environment.
Why create-event is rated Medium
This tool creates new calendar events, which is a reversible Write operation. While calendar events can be deleted, the primary action is creation and modification of data. Severity is medium because misuse could flood a user's calendar with unwanted events, cause schedule conflicts, or disrupt meeting planning, but does not involve data destruction, financial transactions, or code execution.
From the tool's definition Tool name 'create-event' and description stating 'Create calendar event' with creation of persistent calendar entries that can recur. The tool creates new data (calendar events) that persists in Google Calendar.
Attacks that exploit this kind of access
The rule that runs create-event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-event, this is the rule to start with:
create-event 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 MCP Google Workspace, apply this rule, and every create-event call is checked against it from then on.
Questions about create-event
Create calendar event. Returns: created event with id, htmlLink, start, end, status. Use when: scheduling new appointments/meetings. Note: supports recurring events via recurrence. It is categorised as a Write tool in the MCP Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for create-event: 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. Nothing to install.
create-event 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 create-event 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 create-event. 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.
create-event is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue