update_task · Google Connections MCP: Risk & Policy

WHAT IT DOES

What update_task does on Google Connections

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

WHY IT NEEDS A POLICY

Why update_task needs a policy

This tool modifies task records reversibly—changes can be undone by subsequent updates. It does not execute arbitrary code, delete data permanently, or move money. The blast radius is limited to the user's task data. Low severity because task updates are routine operations with minimal downstream impact and no permanent destruction.

From the tool's definition Tool name 'update_task' and description 'Update a Google Task' indicate modifying existing task data. The server description notes 'full CRUD operations' where Update is the 'U' in CRUD, confirming write semantics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_task Rate-limited

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

FAQ

Questions about update_task

What does the update_task tool do? +

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

How do I enforce a policy on update_task? +

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

What risk level is update_task? +

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

Can I rate-limit update_task? +

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

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

update_task is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.