google-workspace.tasks_move
Move a Google Tasks task within its list
This record as markdown: /tools/cowork-os/google-workspace.tasks-move.md
What google-workspace.tasks_move does on CoWork OS
AI agents use google-workspace.tasks_move to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why google-workspace.tasks_move is rated Medium
Moving a task reorders data within a list but does not create, delete, or execute external operations. It is a Write operation because it modifies data (task position) reversibly. Severity is medium because misuse could disrupt task organization and workflow, but the action is easily undone by moving the task again.
From the tool's definition "Move a Google Tasks task within its list" - this modifies the position/order of a task, which is a reversible change to data structure without deletion.
Attacks that exploit this kind of access
The rule that runs google-workspace.tasks_move safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.tasks_move, this is the rule to start with:
google-workspace.tasks_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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every google-workspace.tasks_move call is checked against it from then on.
Questions about google-workspace.tasks_move
Move a Google Tasks task within its list. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.tasks_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 CoWork OS. Nothing to install.
google-workspace.tasks_move 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 google-workspace.tasks_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.
Set action: deny in the PolicyLayer policy for google-workspace.tasks_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.
google-workspace.tasks_move is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue