transfer_calendar_event · GAM MCP Server MCP: Risk & Policy

WHAT IT DOES

What transfer_calendar_event does on GAM MCP Server

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

WHY IT NEEDS A POLICY

Why transfer_calendar_event needs a policy

The name implies moving/transferring a calendar event, which is a Write operation (modifying ownership or location of data). However, depending on implementation it could be destructive (removing from original owner) or execute (triggering external operations). With an empty description, confidence is reduced.

From the tool's definition Tool name 'transfer_calendar_event' on a Google Workspace admin server managing calendar resources; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_calendar_event Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_calendar_event": {
      "limits": [
        {
          "counter": "transfer_calendar_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 GAM MCP Server, so you can run agents against it safely.

FAQ

Questions about transfer_calendar_event

What does the transfer_calendar_event tool do? +

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

How do I enforce a policy on transfer_calendar_event? +

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

What risk level is transfer_calendar_event? +

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

Can I rate-limit transfer_calendar_event? +

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

How do I block transfer_calendar_event completely? +

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

What MCP server provides transfer_calendar_event? +

transfer_calendar_event is provided by the GAM MCP Server MCP server (ktibbs9417/gamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.