Lists all configured Google accounts that can be used with the calendar tools. This tool does not require a user_id as it lists available accounts before selection.
AI agents call calendar_list_accounts to retrieve information from MCP Google Workspace Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available accounts for informational purposes only. There are no side effects, data modifications, deletions, or financial implications. The blast radius of misuse is minimal—an attacker gains visibility into which accounts are configured but cannot authenticate as those accounts or perform actions on them. This is a classic Read operation.
From the tool's definition Tool name and description indicate it 'Lists all configured Google accounts' — a retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access calendar_list_accounts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Workspace Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_list_accounts:
{
"version": "1",
"default": "deny",
"tools": {
"calendar_list_accounts": {}
}
} calendar_list_accounts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all configured Google accounts that can be used with the calendar tools. This tool does not require a user_id as it lists available accounts before selection. It is categorised as a Read tool in the MCP Google Workspace Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Workspace Server MCP server in PolicyLayer and add a rule for calendar_list_accounts: 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 MCP Google Workspace Server. Nothing to install.
calendar_list_accounts 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 calendar_list_accounts 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 calendar_list_accounts. 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.
calendar_list_accounts is provided by the MCP Google Workspace Server MCP server (j3k0/mcp-google-workspace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Google Workspace Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 MCP Google Workspace Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.