This record as markdown: /tools/heznpc-airmcp/list-calendars.md
What list_calendars does on AirMCP
AI agents call list_calendars 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 list_calendars is rated Low
This tool retrieves metadata about calendars (names, colors, writable status) without creating, modifying, deleting, or executing any operations. It is a straightforward query/list operation with no capability to alter system state. The severity is low because calendar enumeration presents minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'List all calendars with name, color, and writable status' — a purely informational retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_calendars 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 list_calendars, this is the rule to start with:
list_calendars 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 list_calendars call is checked against it from then on.
Questions about list_calendars
List all calendars with name, color, and writable status. 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 list_calendars: 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.
list_calendars 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_calendars 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_calendars. 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_calendars 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