List calendar events in a date range. The start_date should always use the time such that it represents the beginning of that day (00:00:00). The end_date should always use the time such that it represents the end of that day (23:59:59). This way, range based searches are always inclusive and can...
AI agents call list_events to retrieve information from MCP iCal Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event data without side effects. It performs a read-only query operation constrained by date range and optional calendar name, typical of Read category tools. The severity is low because exposure of calendar event listings poses minimal risk—at worst, an AI agent could enumerate events across date ranges, which is informational with no destructive or financial impact.
From the tool's definition Tool name is 'list_events' and description states 'List calendar events in a date range.' It accepts date range parameters and optional calendar filtering to retrieve/query events. No modification, deletion, or execution of external operations is performed.
Documented attack patterns abuse exactly the kind of access list_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP iCal Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_events:
{
"version": "1",
"default": "deny",
"tools": {
"list_events": {}
}
}list_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List calendar events in a date range. The start_date should always use the time such that it represents the beginning of that day (00:00:00). The end_date should always use the time such that it represents the end of that day (23:59:59). This way, range based searches are always inclusive and can locate all events in that date range. Args: start_date: Start date in ISO8601 format (YYYY-MM-DDT00:00:00). end_date: Optional end date in ISO8601 format (YYYY-MM-DDT23:59:59). calendar_name: Optional calendar name to filter by. It is categorised as a Read tool in the MCP iCal Server MCP Server, which means it retrieves data without modifying state.
Register the MCP iCal Server MCP server in PolicyLayer and add a rule for list_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 iCal Server. Nothing to install.
list_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 list_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 list_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.
list_events is provided by the MCP iCal Server MCP server (omar-v2/mcp-ical). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MCP iCal Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MCP iCal Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.