task_move · Google Workspace MCP: Risk & Policy

WHAT IT DOES

What task_move does on Google Workspace

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

WHY IT NEEDS A POLICY

Why task_move needs a policy

The tool creates or modifies data reversibly by changing task relationships and positions. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial operations (would be Financial). The modification is reversible—tasks can be repositioned again.

From the tool's definition Tool performs 'Reposition a task' operation, modifying task hierarchy and ordering by setting `parent` (for subtask relationship) and `previous` (for list positioning). These are reversible structural modifications to tasks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_move Rate-limited

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

FAQ

Questions about task_move

What does the task_move tool do? +

Reposition a task: under parent (as a subtask) and/or after previous in the same list. It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task_move? +

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

What risk level is task_move? +

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

Can I rate-limit task_move? +

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

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

task_move is provided by the Google Workspace MCP server (rajool/google-workspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.