google_calendar_update_events

WHAT IT DOES

What google_calendar_update_events does on ContextCore MCP

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

WHY IT NEEDS A POLICY

Why google_calendar_update_events needs a policy

The tool name clearly denotes updating (modifying) calendar events, which is a reversible Write operation. While the empty description reduces confidence slightly, the naming convention and sibling tool context (create/delete patterns) strongly indicate this performs calendar event modifications.

From the tool's definition Tool name 'google_calendar_update_events' explicitly indicates modification of calendar events. Sibling tools include 'google_calendar_create_events' (Write) and 'google_calendar_delete_events' (Destructive), placing this tool in the Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

google_calendar_update_events Rate-limited

google_calendar_update_events 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": {
    "google_calendar_update_events": {
      "limits": [
        {
          "counter": "google_calendar_update_events_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 ContextCore MCP, so you can run agents against it safely.

FAQ

Questions about google_calendar_update_events

What does the google_calendar_update_events tool do? +

google_calendar_update_events. It is categorised as a Write tool in the ContextCore MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on google_calendar_update_events? +

Register the ContextCore MCP server in PolicyLayer and add a rule for google_calendar_update_events: 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 ContextCore MCP. Nothing to install.

What risk level is google_calendar_update_events? +

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

Can I rate-limit google_calendar_update_events? +

Yes. Add a rate_limit block to the google_calendar_update_events 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 google_calendar_update_events completely? +

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

google_calendar_update_events is provided by the ContextCore MCP server (rkpraveendev/contextcore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.