Updates an existing event in Google Calendar.
AI agents use update_calendar_event to create or update resources in Playwright Stealth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright Stealth environment.
This tool modifies calendar data reversibly—calendar events can be edited or reverted without permanent loss. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). Write is the appropriate classification.
From the tool's definition Tool name is 'update_calendar_event' and description states it 'Updates an existing event in Google Calendar.' The verb 'Updates' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_calendar_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for update_calendar_event:
{
"version": "1",
"default": "deny",
"tools": {
"update_calendar_event": {
"limits": [
{
"counter": "update_calendar_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_calendar_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates an existing event in Google Calendar. It is categorised as a Write tool in the Playwright Stealth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright Stealth 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 Playwright Stealth. 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 Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.