cal_update_event · Hermes Google MCP: Risk & Policy

WHAT IT DOES

What cal_update_event does on Hermes Google

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

WHY IT NEEDS A POLICY

Why cal_update_event needs a policy

This tool modifies existing calendar event data reversibly. It is not destructive (events can be edited again or restored), not financial, and not code execution. Severity is medium because calendar event manipulation affects scheduling/coordination but has limited blast radius compared to financial or destructive operations.

From the tool's definition Tool name 'cal_update_event' indicates modification of calendar events. No description provided, but the pattern of sibling tools (cal_create_event, cal_delete_event, cal_list_events) and the server's stated purpose (manage Gmail, Google Calendar, Google…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cal_update_event Rate-limited

cal_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": {
    "cal_update_event": {
      "limits": [
        {
          "counter": "cal_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 Hermes Google, so you can run agents against it safely.

FAQ

Questions about cal_update_event

What does the cal_update_event tool do? +

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

How do I enforce a policy on cal_update_event? +

Register the Hermes Google MCP server in PolicyLayer and add a rule for cal_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 Hermes Google. Nothing to install.

What risk level is cal_update_event? +

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

Can I rate-limit cal_update_event? +

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

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

cal_update_event is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.