Search for events by keyword
AI agents call search_events to retrieve information from AI Calendar Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search_events tool retrieves and filters calendar event data based on keyword criteria. This is a read-only operation with no side effects, no data modification, and no destructive actions. Even if an AI agent misuses it by searching for sensitive event information, the blast radius is limited to information disclosure within the user's own calendar, making this a low-severity risk.
From the tool's definition Tool name is 'search_events' and description states 'Search for events by keyword' — a query operation that retrieves matching calendar events without modifying or deleting data.
Attacks that exploit this kind of access
Search for events by keyword. It is categorised as a Read tool in the AI Calendar Assistant MCP Server, which means it retrieves data without modifying state.
Register the AI Calendar Assistant 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 AI Calendar Assistant. Nothing to install.
search_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 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.
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.
search_events is provided by the AI Calendar Assistant MCP server (othmane-zizi-pro/ai-calendar-assistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →