This record as markdown: /tools/heznpc-airmcp/today-events.md
What today_events does on AirMCP
AI agents call today_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 today_events is rated Low
This tool retrieves calendar event data without modifying, deleting, or executing any operations. It is purely informational and has no blast radius if misused by an AI agent—the worst outcome is exposure of the user's calendar schedule, which is a read-only disclosure risk rather than a destructive or operational risk.
From the tool's definition Tool name 'today_events' and description 'Get all calendar events for today' indicate a retrieval operation with no side effects. The verb 'Get' explicitly denotes a query action.
Attacks that exploit this kind of access
The rule that runs today_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 today_events, this is the rule to start with:
today_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 today_events call is checked against it from then on.
Questions about today_events
Get all calendar events for today. 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 today_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.
today_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 today_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 today_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.
today_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