calendar_update_event · Vibe MCP: Risk & Policy

WHAT IT DOES

What calendar_update_event does on VibeMCP

AI agents use calendar_update_event to create or update resources in VibeMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VibeMCP environment.

WHY IT NEEDS A POLICY

Why calendar_update_event needs a policy

An AI agent can call calendar_update_event faster than any human can review — one bad instruction and it creates or modifies resources in VibeMCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_update_event Rate-limited

calendar_update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendar_update_event": {
      "limits": [
        {
          "counter": "calendar_update_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeMCP, so you can run agents against it safely.

FAQ

Questions about calendar_update_event

What does the calendar_update_event tool do? +

Update an existing calendar event (Google Calendar or Outlook). It is categorised as a Write tool in the VibeMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calendar_update_event? +

Register the Vibe MCP server in PolicyLayer and add a rule for calendar_update_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 VibeMCP. Nothing to install.

What risk level is calendar_update_event? +

calendar_update_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calendar_update_event? +

Yes. Add a rate_limit block to the calendar_update_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.

How do I block calendar_update_event completely? +

Set action: deny in the PolicyLayer policy for calendar_update_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.

What MCP server provides calendar_update_event? +

calendar_update_event is provided by the Vibe MCP server (vibetensor/vibemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.