Move a task to another position within the same list, or to a different list via destinationTasklist (task ID is preserved in both cases)
AI agents use move-task to create or update resources in Google Tasks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tasks MCP Server environment.
This tool creates or modifies data reversibly by changing a task's position or list assignment. It does not delete, destroy, or execute arbitrary operations, making it a Write action. Severity is medium because misuse could reorganize many tasks across lists, creating confusion, but changes are fully reversible through subsequent move operations.
From the tool's definition Tool description states 'Move a task to another position' and 'to a different list', which modifies task metadata (position/list assignment) without deleting or destroying data. The task ID is preserved, confirming reversibility.
Documented attack patterns abuse exactly the kind of access move-task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Tasks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move-task:
{
"version": "1",
"default": "deny",
"tools": {
"move-task": {
"limits": [
{
"counter": "move-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move-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.
Free to start. No card required.
Move a task to another position within the same list, or to a different list via destinationTasklist (task ID is preserved in both cases). It is categorised as a Write tool in the Google Tasks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for move-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 Tasks MCP Server. Nothing to install.
move-task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move-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.
Set action: deny in the PolicyLayer policy for move-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.
move-task is provided by the Google Tasks MCP Server MCP server (arpitbatra123/mcp-googletasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Tasks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.