Low Risk

get_upcoming_events

Get upcoming events from moodle

How to control get_upcoming_events ↓

What get_upcoming_events does on Moodle-MCP

AI agents call get_upcoming_events to retrieve information from Moodle-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_upcoming_events needs a policy

This tool retrieves calendar/event data from Moodle LMS without side effects. It queries existing data (upcoming events) and returns results. No data is created, modified, deleted, or executed. This is a straightforward read operation with minimal risk—misuse would only expose event information already accessible to authenticated Moodle users.

From the tool's definition Tool name 'get_upcoming_events' and description 'Get upcoming events from moodle' indicate a retrieval operation with no modification, deletion, or execution of external code.

Documented attack patterns abuse exactly the kind of access get_upcoming_events gives an agent:

How to control get_upcoming_events

PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_upcoming_events:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_upcoming_events": {}
  }
}

get_upcoming_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Moodle-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_upcoming_events

What does the get_upcoming_events tool do? +

Get upcoming events from moodle. It is categorised as a Read tool in the Moodle-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_upcoming_events? +

Register the Moodle- MCP server in PolicyLayer and add a rule for get_upcoming_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-MCP. Nothing to install.

What risk level is get_upcoming_events? +

get_upcoming_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_upcoming_events? +

Yes. Add a rate_limit block to the get_upcoming_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.

How do I block get_upcoming_events completely? +

Set action: deny in the PolicyLayer policy for get_upcoming_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.

What MCP server provides get_upcoming_events? +

get_upcoming_events is provided by the Moodle- MCP server (loyaniu/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Moodle-MCP tool call.

Start from Moodle-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 Moodle-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.