AI agents use create_calendar_event to create or update resources in Gg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gg environment.
Creating a calendar event is a reversible write operation that adds new data to the user's calendar. It does not delete, execute arbitrary operations, or involve financial transactions. While it could cause scheduling conflicts or inconvenience if misused, the effect is reversible (the event can be deleted).
From the tool's definition Tool description states 'Create a calendar event', which is a write operation that creates new data in Google Calendar.
Attacks that exploit this kind of access
Create a calendar event. format: YYYY-MM-DDTHH:MM (VN Time). It is categorised as a Write tool in the Gg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gg MCP server in PolicyLayer and add a rule for create_calendar_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 Gg. Nothing to install.
create_calendar_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_calendar_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_calendar_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_calendar_event is provided by the Gg MCP server (tannht/google-cloud-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 →