calendar_create_event
Create a new event in Google Calendar. Specify the title, start time, end time, and optionally invite attendees. Use ISO 8601 format for dates (e.g., 2024-12-15T14:00:00).
This record as markdown: /tools/io-github-saloprj-dialogbrain/calendar-create-event.md
What calendar_create_event does on Dialogbrain
AI agents use calendar_create_event to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | — | Event end time in ISO 8601 format. If not provided, defaults to 1 hour after start. Also accepts 'end_time' as alias. |
start | string | — | Event start time in ISO 8601 format (e.g., 2024-12-15T14:00:00). Also accepts 'start_time' as alias. |
title | string | — | Alias for summary - event title. |
summary | string | — | Event title/summary. Required. Also accepts 'title' as alias. |
end_time | string | — | Alias for end - event end time. |
location | string | — | Event location (physical address or virtual meeting link). |
timezone | string | — | Timezone for the event (e.g., 'America/New_York', 'UTC'). |
attendees | array | — | List of attendee email addresses to invite. |
start_time | string | — | Alias for start - event start time in ISO 8601 format. |
calendar_id | string | — | Calendar ID to create event in. Defaults to primary calendar. |
description | string | — | Event description/notes. |
add_google_meet | boolean | — | If true, automatically creates a Google Meet link for the event. OMIT to skip Meet link. |
Parameters from the server's own tool schema.
Why calendar_create_event is rated Medium
This tool creates new calendar entries, which is a reversible write operation. It modifies calendar state by adding an event but does not execute arbitrary code, delete data, or move money. Severity is medium because misuse could create numerous unwanted calendar events causing schedule disruption and confusion, but the impact is contained to calendar data and can be undone by deletion.
From the tool's definition Tool description states "Create a new event in Google Calendar" with parameters for title, start time, end time, and optional attendees. The verb "create" and action of adding a calendar event represents data modification.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs calendar_create_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar_create_event, this is the rule to start with:
calendar_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 Dialogbrain, apply this rule, and every calendar_create_event call is checked against it from then on.
Questions about calendar_create_event
Create a new event in Google Calendar. Specify the title, start time, end time, and optionally invite attendees. Use ISO 8601 format for dates (e.g., 2024-12-15T14:00:00). It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
calendar_create_event accepts 12 parameters: end, start, title, summary, end_time, location, timezone, attendees, start_time, calendar_id, description, add_google_meet. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for calendar_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 Dialogbrain. Nothing to install.
calendar_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 calendar_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 calendar_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.
calendar_create_event is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue