Low Risk

tasks_tasklists_list

List all task lists

Part of the Google Workspace Tasks (gws CLI) server.

tasks_tasklists_list is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GOOGLE WORKSPACE TASKS (GWS CLI) →

Free to start. No card required.

AI agents call tasks_tasklists_list to retrieve information from Google Workspace Tasks (gws CLI) without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though tasks_tasklists_list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tasks_tasklists_list": {}
  }
}

See the full Google Workspace Tasks (gws CLI) policy for all 14 tools.

Get this rule live on your own Google Workspace Tasks (gws CLI) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GOOGLE WORKSPACE TASKS (GWS CLI) →

View all 14 tools →

These attack patterns abuse exactly the kind of access tasks_tasklists_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so tasks_tasklists_list only ever does what you allow.

SECURE GOOGLE WORKSPACE TASKS (GWS CLI) →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the tasks_tasklists_list tool do? +

List all task lists. It is categorised as a Read tool in the Google Workspace Tasks (gws CLI) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tasks_tasklists_list? +

Register the Google Workspace Tasks (gws CLI) MCP server in PolicyLayer and add a rule for tasks_tasklists_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 Workspace Tasks (gws CLI). Nothing to install.

What risk level is tasks_tasklists_list? +

tasks_tasklists_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tasks_tasklists_list? +

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

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

tasks_tasklists_list is provided by the Google Workspace Tasks (gws CLI) MCP server (@gws mcp -s tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Workspace Tasks (gws CLI) tool call.

Deterministic rules across all 14 Google Workspace Tasks (gws CLI) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.