Create a new calendar event
AI agents use create_calendar_event to create or update resources in Enhanced MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced MCP Server environment.
This tool creates new calendar events, which is a Write operation—it modifies the user's calendar data but is reversible (events can be edited or deleted). Severity is medium because while calendar mismanagement could cause scheduling conflicts or missed appointments, it doesn't result in data loss, financial impact, or irreversible damage.
From the tool's definition Tool name 'create_calendar_event' and description 'Create a new calendar event' indicate data creation/modification. This creates a new calendar entry, which is a reversible write operation.
Attacks that exploit this kind of access
Create a new calendar event. It is categorised as a Write tool in the Enhanced MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced MCP Server 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 Enhanced MCP Server. 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 Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →