move_task_to_list · Google Connections MCP: Risk & Policy

WHAT IT DOES

What move_task_to_list does on Google Connections

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

Moving a task between lists is a reversible modification operation that changes task assignment/organization but does not delete data, execute external code, or create financial obligations. This fits the Write category (creates or modifies data reversibly). Severity is low because task reorganization has minimal blast radius and is easily undone by moving the task back to its original list.

From the tool's definition Tool name 'move_task_to_list' and description 'Move a task between lists' indicate modification of task metadata/state without deletion or creation of new tasks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_task_to_list Rate-limited

move_task_to_list 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": {
    "move_task_to_list": {
      "limits": [
        {
          "counter": "move_task_to_list_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 move_task_to_list

What does the move_task_to_list tool do? +

Move a task between lists. 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 move_task_to_list? +

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

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

Can I rate-limit move_task_to_list? +

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

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

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