Aggregated daily summary: overdue count, today's deadlines, recent grades, upcoming events, actionable tasks
AI agents call daily_briefing 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 is a read-only tool that queries and summarizes information from Moodle LMS. It retrieves and aggregates data without any side effects. The aggregation of existing data points (counts, dates, grades) constitutes information retrieval. Severity is low because exposure of a daily briefing summary presents minimal risk—it contains only data the user already has access to in disaggregated form.
From the tool's definition Tool performs aggregation and retrieval of existing data: 'overdue count', 'today's deadlines', 'recent grades', 'upcoming events', 'actionable tasks'. No modification, deletion, execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access daily_briefing 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 daily_briefing:
{
"version": "1",
"default": "deny",
"tools": {
"daily_briefing": {}
}
} daily_briefing 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.
Aggregated daily summary: overdue count, today's deadlines, recent grades, upcoming events, actionable tasks. 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 daily_briefing: 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.
daily_briefing 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 daily_briefing 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 daily_briefing. 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.
daily_briefing 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.