// MCP TOOL REFERENCE

GOOGLE WORKSPACE TASKS (GWS CLI) TOOLS

14 tools from the Google Workspace Tasks (gws CLI) MCP Server, categorised by risk level.

View the Google Workspace Tasks (gws CLI) policy →

READ TOOLS

tasks_tasklists_get Get a task list by ID 2/5 tasks_tasklists_list List all task lists 2/5 tasks_tasks_get Get a task by ID 2/5 tasks_tasks_list List tasks in a task list 2/5

WRITE TOOLS

tasks_tasklists_insert Create a new task list 3/5 tasks_tasklists_patch Patch a task list 3/5 tasks_tasklists_update Update a task list 3/5 tasks_tasks_insert Create a new task 3/5 tasks_tasks_move Move a task to different position or parent 3/5 tasks_tasks_patch Patch a task 3/5 tasks_tasks_update Update a task 3/5

DESTRUCTIVE TOOLS

tasks_tasklists_delete Permanently delete a task list 5/5 tasks_tasks_clear Clear all completed tasks from a list 5/5 tasks_tasks_delete Permanently delete a task 5/5

// FAQ

How many tools does the Google Workspace Tasks (gws CLI) MCP server have? +

The Google Workspace Tasks (gws CLI) MCP server exposes 14 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Google Workspace Tasks (gws CLI) tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Google Workspace Tasks (gws CLI) server.

What risk categories do Google Workspace Tasks (gws CLI) tools fall into? +

Google Workspace Tasks (gws CLI) tools are categorised as Read (4), Write (7), Destructive (3). Each category has a recommended default policy.

Enforce policies on Google Workspace Tasks (gws CLI)

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →