gmail_calendar_read_event

Read full details of a single event including description, attendees, and recurrence.

Server Personal Gmail jaingxyz/personal-gmail-mcp
Category Read
Risk class Low
Parameters 00 required

What gmail_calendar_read_event does on Personal Gmail

AI agents call gmail_calendar_read_event to retrieve information from Personal Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why gmail_calendar_read_event needs a policy

This tool retrieves and queries calendar event data without side effects. It matches the Read category: it fetches existing data (event details, description, attendees, recurrence) without creating, modifying, or deleting anything. Low severity because unauthorized access to a single calendar event, while a privacy concern, has limited blast radius compared to tools that could modify or delete events or send emails.

From the tool's definition Tool name includes 'read' and description states 'Read full details of a single event' — retrieves event information with no modification or deletion.

Questions about gmail_calendar_read_event

What does the gmail_calendar_read_event tool do? +

Read full details of a single event including description, attendees, and recurrence. It is categorised as a Read tool in the Personal Gmail MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gmail_calendar_read_event? +

Register the Personal Gmail MCP server in PolicyLayer and add a rule for gmail_calendar_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 Personal Gmail. Nothing to install.

What risk level is gmail_calendar_read_event? +

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

Can I rate-limit gmail_calendar_read_event? +

Yes. Add a rate_limit block to the gmail_calendar_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 gmail_calendar_read_event completely? +

Set action: deny in the PolicyLayer policy for gmail_calendar_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 gmail_calendar_read_event? +

gmail_calendar_read_event is provided by the Personal Gmail MCP server (jaingxyz/personal-gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.