moodle_get_calendar_events
Get upcoming calendar events (assignments due, quizzes opening, etc.), optionally filtered to one course. Defaults to the next 30 days.
This record as markdown: /tools/1alexandrer-moodle-mcp/moodle-get-calendar-events.md
What moodle_get_calendar_events does on Moodle
AI agents call moodle_get_calendar_events to retrieve information from Moodle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why moodle_get_calendar_events is rated Low
This tool queries and retrieves calendar event data from Moodle without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with minimal blast radius if misused—an agent could only retrieve information about upcoming events that the authenticated user already has access to view in Moodle.
From the tool's definition Tool name 'moodle_get_calendar_events' and description 'Get upcoming calendar events' indicate a retrieval operation with no side effects. The description explicitly lists read-only use cases: 'assignments due, quizzes opening, etc.' with optional filtering.
Attacks that exploit this kind of access
The rule that runs moodle_get_calendar_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Moodle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For moodle_get_calendar_events, this is the rule to start with:
moodle_get_calendar_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every moodle_get_calendar_events call is checked against it from then on.
Questions about moodle_get_calendar_events
Get upcoming calendar events (assignments due, quizzes opening, etc.), optionally filtered to one course. Defaults to the next 30 days. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
Register the Moodle MCP server in PolicyLayer and add a rule for moodle_get_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 Moodle. Nothing to install.
moodle_get_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 moodle_get_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 moodle_get_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.
moodle_get_calendar_events is provided by the Moodle MCP server (1alexandrer/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Moodle, and thousands of servers like it.
This server
Across the catalogue