Get upcoming calendar events and due dates (assignments, quizzes, exams) for a course.
AI agents call get_upcoming to retrieve information from Waterloo Learn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays calendar events and due dates for a course. It is a read-only operation with no state changes, reversible actions, code execution, data destruction, or financial implications. The low severity reflects minimal risk even if misused by an agent, as it only exposes course deadline information already accessible to the authenticated user.
From the tool's definition Tool name and description indicate retrieval only: 'Get upcoming calendar events and due dates' — queries course information without modification, creation, or deletion. No side effects beyond data retrieval.
Attacks that exploit this kind of access
Get upcoming calendar events and due dates (assignments, quizzes, exams) for a course. It is categorised as a Read tool in the Waterloo Learn MCP Server, which means it retrieves data without modifying state.
Register the Waterloo Learn MCP server in PolicyLayer and add a rule for get_upcoming: 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 Waterloo Learn. Nothing to install.
get_upcoming 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_upcoming 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_upcoming. 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_upcoming is provided by the Waterloo Learn MCP server (petersenmatthew/waterloo-learn-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 →