This record as markdown: /tools/heznpc-airmcp/gws-calendar-list.md
What gws_calendar_list does on AirMCP
AI agents call gws_calendar_list to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gws_calendar_list is rated Low
This tool queries calendar data and returns a list of events—a read-only operation. It retrieves information without creating, modifying, deleting, executing external commands, or committing financial obligations. The blast radius of misuse is minimal (exposure of calendar event metadata). Confidence is high because the description is explicit about the retrieval nature of the operation.
From the tool's definition Tool name 'gws_calendar_list' and description 'List upcoming events from Google Calendar' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs gws_calendar_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gws_calendar_list, this is the rule to start with:
gws_calendar_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every gws_calendar_list call is checked against it from then on.
Questions about gws_calendar_list
List upcoming events from Google Calendar. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for gws_calendar_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 AirMCP. Nothing to install.
gws_calendar_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 gws_calendar_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 gws_calendar_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.
gws_calendar_list is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue