List calendar events. Optionally filter by course_id and an ISO date range
AI agents call list_calendar_events to retrieve information from PokeCanvas 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 from Canvas LMS with optional filtering. No data is created, modified, deleted, or executed. The action is a standard read/query operation with minimal security risk—a misused tool would only return unintended but already-existing calendar data visible within the user's Canvas access scope.
From the tool's definition Tool name 'list_calendar_events' and description 'List calendar events' indicate retrieval of existing data without modification. The server description notes 'Reads live data on every request' confirming read-only operations.
Attacks that exploit this kind of access
List calendar events. Optionally filter by course_id and an ISO date range. It is categorised as a Read tool in the PokeCanvas MCP Server, which means it retrieves data without modifying state.
Register the PokeCanvas MCP server in PolicyLayer and add a rule for list_calendar_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 PokeCanvas. Nothing to install.
list_calendar_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_calendar_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_calendar_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_calendar_events is provided by the PokeCanvas MCP server (jackulau/pokecanvas). 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 →