search-events

Search events by text. Returns: filtered array of events matching query in summary/description/location. Use when: finding specific events by keyword. Note: single calendar only.

SERVERMCP Google Workspace SOURCE199-mcp/mcp-google

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/199-biotechnologies-mcp-google/search-events.md

WHAT IT DOES

What search-events does on MCP Google Workspace

AI agents call search-events to retrieve information from MCP Google Workspace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search-events is rated Low

This tool queries and retrieves calendar events matching search criteria without creating, modifying, or deleting any data. It has no side effects beyond information retrieval. While Google Workspace access can be sensitive (calendar data is personal), the read-only nature and limitation to 'single calendar only' constrains blast radius to low severity.

From the tool's definition Tool description states 'Search events by text. Returns: filtered array of events matching query' — a retrieval operation with no mutation of data. The name 'search-events' and function of filtering/returning matching events confirms read-only behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search-events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search-events, this is the rule to start with:

search-events Allowed

search-events 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": {
    "search-events": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every search-events call is checked against it from then on.

FAQ

Questions about search-events

What does the search-events tool do? +

Search events by text. Returns: filtered array of events matching query in summary/description/location. Use when: finding specific events by keyword. Note: single calendar only. It is categorised as a Read tool in the MCP Google Workspace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-events? +

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

What risk level is search-events? +

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

Can I rate-limit search-events? +

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

How do I block search-events completely? +

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

What MCP server provides search-events? +

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

KEEP EXPLORING

More on MCP Google Workspace, and thousands of servers like it.

This server

All 26 MCP Google Workspace tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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