Get upcoming assignment deadlines across all courses, sorted by due date
AI agents call get_upcoming_deadlines 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.
This tool queries and retrieves existing deadline information from the Moodle LMS. It performs a read-only operation that sorts and returns data without side effects, reversible actions, code execution, destructive operations, or financial impact. The retrieval of calendar/deadline metadata poses minimal security risk.
From the tool's definition Tool name 'get_upcoming_deadlines' and description 'Get upcoming assignment deadlines across all courses, sorted by due date' indicate data retrieval with no modification, creation, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_upcoming_deadlines gives an agent:
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_deadlines:
{
"version": "1",
"default": "deny",
"tools": {
"get_upcoming_deadlines": {}
}
} get_upcoming_deadlines is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get upcoming assignment deadlines across all courses, sorted by due date. It is categorised as a Read tool in the Moodle-MCP MCP Server, which means it retrieves data without modifying state.
Register the Moodle- MCP server in PolicyLayer and add a rule for get_upcoming_deadlines: 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.
get_upcoming_deadlines 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_deadlines 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_deadlines. 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_deadlines 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.
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.