AI agents use create_flight_event to create or update resources in Gcal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gcal environment.
This tool creates new calendar events (reversible write operation). While calendar modifications are generally low-risk, the medium severity accounts for potential misuse scenarios such as creating fake flight events to mislead the user, pollute their calendar with spam, or create scheduling conflicts. The write is reversible (events can be deleted), so this does not rise to Destructive.
From the tool's definition Tool description states it will "Create a Google Calendar event" which is a write operation that creates new data in Google Calendar.
Attacks that exploit this kind of access
Create a Google Calendar event for a flight. Provide extracted flight details from a confirmation email. The event spans from departure to arrival with timezone-aware times. It is categorised as a Write tool in the Gcal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gcal MCP server in PolicyLayer and add a rule for create_flight_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 Gcal. Nothing to install.
create_flight_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_flight_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_flight_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_flight_event is provided by the Gcal MCP server (kwikkid/gcalcli). 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 →