List the account's task lists (each has an id + title).
AI agents call tasklist_list to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves task list metadata (id and title) from the user's Google Workspace account without creating, modifying, or deleting any data. It is a read-only operation with minimal blast radius if misused by an AI agent—the worst outcome would be unwanted visibility into task list names.
From the tool's definition Tool name 'tasklist_list' and description 'List the account's task lists' indicate a retrieval operation with no side effects. The verb 'list' is explicitly mentioned in the classification rules as a Read category example.
Attacks that exploit this kind of access
List the account's task lists (each has an id + title). It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for tasklist_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. Nothing to install.
tasklist_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tasklist_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.
Set action: deny in the PolicyLayer policy for tasklist_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.
tasklist_list 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →