Updates an existing event in Google Calendar.
AI agents use update_calendar_event to create or update resources in Pointsyeah — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pointsyeah environment.
This tool modifies existing calendar events reversibly (updates can be undone or corrected), making it a Write-class action. Severity is medium because misuse could disrupt scheduling/calendars for users, but the blast radius is limited to calendar data and doesn't involve deletion, financial transactions, or code execution.
From the tool's definition Tool description states it 'Updates an existing event in Google Calendar' — a direct modification operation on calendar data.
Attacks that exploit this kind of access
Updates an existing event in Google Calendar. It is categorised as a Write tool in the Pointsyeah MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for update_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 Pointsyeah. Nothing to install.
update_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 update_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 update_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.
update_calendar_event is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). 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 →