quick_add_task · Gcal MCP: Risk & Policy

WHAT IT DOES

What quick_add_task does on Gcal

AI agents use quick_add_task 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 quick_add_task needs a policy

This tool creates new data (a task) and modifies calendar state by scheduling it, which are reversible write operations. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve money (ruling out Financial). While it writes to calendar data, the blast radius is limited to task/calendar entries that can be edited or deleted if needed.

From the tool's definition Tool description states "Create a task and schedule it in one call" - the word "Create" indicates a write operation that modifies calendar and task data by adding new entries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quick_add_task Rate-limited

quick_add_task 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": {
    "quick_add_task": {
      "limits": [
        {
          "counter": "quick_add_task_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 quick_add_task

What does the quick_add_task tool do? +

Create a task and schedule it in one call. Combines add_task + schedule_task. Provide task details plus a date/time/timezone for the calendar block. 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 quick_add_task? +

Register the Gcal MCP server in PolicyLayer and add a rule for quick_add_task: 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 quick_add_task? +

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

Can I rate-limit quick_add_task? +

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

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

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