calendar_get_event

THE RISK

Low Risk

Why calendar_get_event needs a policy

This tool retrieves calendar event data without creating, modifying, or deleting any resources. It is a straightforward read operation that queries Google Calendar for event details. The low severity reflects minimal risk even if misused—information disclosure about calendar events is less damaging than financial, destructive, or write operations.

From the tool's definition Tool name 'calendar_get_event' and description 'Get detailed information about a specific calendar event' indicate a retrieval operation with no modifications or side effects.

Documented attack patterns abuse exactly the kind of access calendar_get_event gives an agent:

POLICY

How to control calendar_get_event

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_get_event:

policy.json

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

calendar_get_event is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Google Workspace — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Workspace tools

Destructive drive_delete_comment Delete a comment from a Google Doc. Args: - file_id (string): The ID of the Google Doc Destructive sheets_clear_values Clear cell values from a specific range in a Google Spreadsheet (keeps formatting). Args: Write docs_batch_update Apply batch updates to a Google Doc (insert/update/delete text, formatting, images, tables Write docs_create_document Create a new Google Doc with an optional initial body. Args: - title (string): The titl Write sheets_append_values Append rows of data to the end of a table in a Google Spreadsheet. Args: - spreadsheet_ Write sheets_duplicate_sheet Duplicate a sheet within the same spreadsheet. Args: - spreadsheet_id (string): The ID Write drive_copy_file Create a copy of a file in Google Drive. Args: - file_id (string): The ID of the file t Write drive_create_comment Add a comment to a Google Doc. Can be anchored to specific text or unanchored. Args: -

All 34 Google Workspace tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about calendar_get_event

What does the calendar_get_event tool do? +

Get detailed information about a specific calendar event. Args: - calendar_id (string): Calendar ID (default:. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar_get_event? +

Register the Google Workspace MCP server in PolicyLayer and add a rule for calendar_get_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 Google Workspace. Nothing to install.

What risk level is calendar_get_event? +

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

Can I rate-limit calendar_get_event? +

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

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

calendar_get_event is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Workspace tool call.

Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →