modify_event

Modify an existing event in a Google Calendar

SERVERVaultAssist SOURCE3xcaffeine/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3xcaffeine-mcp-server/modify-event.md

WHAT IT DOES

What modify_event does on VaultAssist

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

RISK

Why modify_event is rated Medium

This tool modifies calendar events, which is a reversible operation (changes can be undone by modifying again or reverting to previous state). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or retrieve data without side effects (Read).

From the tool's definition Tool name 'modify_event' and description 'Modify an existing event in a Google Calendar' indicate creation or modification of data in a reversible manner.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs modify_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultAssist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For modify_event, this is the rule to start with:

modify_event Rate-limited

modify_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": {
    "modify_event": {
      "limits": [
        {
          "counter": "modify_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultAssist, apply this rule, and every modify_event call is checked against it from then on.

FAQ

Questions about modify_event

What does the modify_event tool do? +

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

How do I enforce a policy on modify_event? +

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

What risk level is modify_event? +

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

Can I rate-limit modify_event? +

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

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

modify_event is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultAssist, and thousands of servers like it.

This server

All 79 VaultAssist tools →

Across the catalogue

calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →