Create an event using natural language (e.g.,
AI agents use quick_add_event to create or update resources in Google Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Calendar MCP environment.
quick_add_event creates calendar events, which is a Write operation (data modification without deletion or irreversibility). Severity is medium because misuse could spam or pollute a calendar, but events can be deleted and the action is easily reversible. Confidence is high due to clear 'Create' language in the description.
From the tool's definition Tool description states 'Create an event using natural language' — explicitly a creation action that modifies calendar data reversibly.
Attacks that exploit this kind of access
Create an event using natural language (e.g.,. It is categorised as a Write tool in the Google Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Calendar MCP server in PolicyLayer and add a rule for quick_add_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 Google Calendar MCP. Nothing to install.
quick_add_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 quick_add_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 quick_add_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.
quick_add_event is provided by the Google Calendar MCP server (paytience/google-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →