create_tickler · Gcal MCP: Risk & Policy

WHAT IT DOES

What create_tickler does on Gcal

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

WHY IT NEEDS A POLICY

Why create_tickler needs a policy

This tool creates a new calendar entry (a tickler/reminder event) on a user's calendar. Creating calendar events is reversible data modification (events can be deleted), so it falls under Write rather than Destructive. Severity is medium because misuse could clutter a calendar with unwanted events, but the impact is limited to calendar organization and can be easily remedied by deleting events.

From the tool's definition Tool creates a calendar event ('Creates a 15-minute calendar event titled'), which is a data modification action. The term 'create' and explicit mention of creating a calendar event confirm this is a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_tickler Rate-limited

create_tickler 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": {
    "create_tickler": {
      "limits": [
        {
          "counter": "create_tickler_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 Gcal, so you can run agents against it safely.

FAQ

Questions about create_tickler

What does the create_tickler tool do? +

Set a reminder to revisit a task on a future date. Creates a 15-minute calendar event titled. It is categorised as a Write tool in the Gcal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_tickler? +

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

What risk level is create_tickler? +

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

Can I rate-limit create_tickler? +

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

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

create_tickler is provided by the Gcal MCP server (kwikkid/gcalcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.