List all task lists in the user account
AI agents call list_task_lists to retrieve information from Calendar Mcp 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 data about task lists without creating, modifying, deleting, or executing operations. It has no side effects and follows the Read pattern (list, get, fetch). The blast radius of misuse is minimal—an attacker gains visibility into task organization but cannot alter state or trigger actions.
From the tool's definition Tool name 'list_task_lists' and description 'List all task lists in the user account' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
List all task lists in the user account. It is categorised as a Read tool in the Calendar Mcp MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP server in PolicyLayer and add a rule for list_task_lists: 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 Calendar Mcp. Nothing to install.
list_task_lists 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 list_task_lists 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 list_task_lists. 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.
list_task_lists is provided by the Calendar MCP server (ydrogen/calendar-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 →