Retrieve calendar events within a specific date range
AI agents call get-events-by-date-range to retrieve information from Calendar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (queries) calendar event data within a specified date range. It has no side effects—it does not create, modify, delete, or execute external operations. It is a straightforward data retrieval function consistent with other sibling tools on the server (get-event-details, get-recent-events, get-todays-events, get-upcoming-events, search-events), all of which are read operations.
From the tool's definition Tool name 'get-events-by-date-range' and description 'Retrieve calendar events within a specific date range' indicate a read-only query operation with no modification or deletion capability.
Attacks that exploit this kind of access
Retrieve calendar events within a specific date range. It is categorised as a Read tool in the Calendar MCP MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP server in PolicyLayer and add a rule for get-events-by-date-range: 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 Calendar MCP. Nothing to install.
get-events-by-date-range 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 get-events-by-date-range 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 get-events-by-date-range. 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.
get-events-by-date-range is provided by the Calendar MCP server (wyattjoh/calendar-mcp). 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 →