Create a Google Calendar event with attendees, notes, and timing.
AI agents use create-event to create or update resources in Universal Mcp Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Universal Mcp Toolkit environment.
This tool creates (write) calendar data reversibly. It does not execute arbitrary code, delete data, or move money. The severity is medium because misuse could schedule unwanted meetings, spam attendees, or trigger calendar-dependent workflows, but the impact is limited to calendar state and can be undone by deletion.
From the tool's definition Tool description states 'Create a Google Calendar event' — a create operation that modifies calendar state by adding a new event with attendees, notes, and timing.
Attacks that exploit this kind of access
Create a Google Calendar event with attendees, notes, and timing. It is categorised as a Write tool in the Universal Mcp Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Universal Mcp Toolkit MCP server in PolicyLayer and add a rule for 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 Universal Mcp Toolkit. Nothing to install.
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 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 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.
create-event is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →