get_upcoming_events
Get the next N upcoming events from now (searches up to 30 days ahead). A convenience wrapper that doesn
This record as markdown: /tools/heznpc-airmcp/get-upcoming-events.md
What get_upcoming_events does on AirMCP
AI agents call get_upcoming_events 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 get_upcoming_events is rated Low
This tool reads upcoming calendar events without creating, modifying, deleting, or executing any actions. It has no side effects and poses minimal risk even if misused by an agent, as the worst outcome is disclosure of the user's calendar schedule. The 30-day search window and read-only nature confirm this is a simple data retrieval (Read) category with low severity.
From the tool's definition Tool name and description indicate it 'Get[s] the next N upcoming events' — a query operation that searches and retrieves calendar data without modification or execution of external actions.
Attacks that exploit this kind of access
The rule that runs get_upcoming_events 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 get_upcoming_events, this is the rule to start with:
get_upcoming_events 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 get_upcoming_events call is checked against it from then on.
Questions about get_upcoming_events
Get the next N upcoming events from now (searches up to 30 days ahead). A convenience wrapper that doesn. 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 get_upcoming_events: 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.
get_upcoming_events 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 get_upcoming_events 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 get_upcoming_events. 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.
get_upcoming_events 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