read_event

Read full details of a calendar event by ID. Includes attendees (read-only), location, description, and recurrence info.

SERVERAirMCP SOURCEairmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/read-event.md

WHAT IT DOES

What read_event does on AirMCP

AI agents call read_event 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.

RISK

Why read_event is rated Low

This tool retrieves calendar event information without modifying, deleting, or executing any operations. It is a straightforward query operation that returns event metadata. The read-only nature of attendee access and absence of any write/execute/destructive capabilities place it firmly in the Read category.

From the tool's definition Tool description states 'Read full details of a calendar event by ID' with read-only access to attendees, location, description, and recurrence info. Name and description both clearly indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_event 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 read_event, this is the rule to start with:

read_event Allowed

read_event is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_event": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every read_event call is checked against it from then on.

FAQ

Questions about read_event

What does the read_event tool do? +

Read full details of a calendar event by ID. Includes attendees (read-only), location, description, and recurrence info. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_event? +

Register the Air MCP server in PolicyLayer and add a rule for read_event: 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.

What risk level is read_event? +

read_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_event? +

Yes. Add a rate_limit block to the read_event 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.

How do I block read_event completely? +

Set action: deny in the PolicyLayer policy for read_event. 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.

What MCP server provides read_event? +

read_event 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.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools →

Across the catalogue

claude_read_file on Claude Bridge →get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →