get_course_completion_status
Read each participant's course completion from the course completion report: whether and when they completed the course, and each criterion met and when; participants as aliases when the server pseudonymizes. Some criteria (a grade, a date, days enrolled) are worked out by Moodle's scheduled task...
This record as markdown: /tools/falkenslab-moodle-mcp/get-course-completion-status.md
What get_course_completion_status does on Moodle
AI agents call get_course_completion_status 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | — | The participant's alias, as the reading tools give it when the server pseudonymizes |
limit | integer | — | How many participants (50 by default, up to 200) |
offset | integer | — | How many participants to skip first (0 by default) |
userId | integer | — | The participant's user id, when the server shows names |
groupId | integer | — | Only this group's participants |
courseId | integer | Yes |
Parameters from the server's own tool schema.
Why get_course_completion_status is rated Low
Even though get_course_completion_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_course_completion_status 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 get_course_completion_status, this is the rule to start with:
get_course_completion_status 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 get_course_completion_status call is checked against it from then on.
Questions about get_course_completion_status
Read each participant's course completion from the course completion report: whether and when they completed the course, and each criterion met and when; participants as aliases when the server pseudonymizes. Some criteria (a grade, a date, days enrolled) are worked out by Moodle's scheduled tasks, so a criterion just met may not show yet. A page at a time: limit participants (50 by default) after skipping offset; more says whether there are others. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
get_course_completion_status accepts 6 parameters: user, limit, offset, userId, groupId, courseId. Required: courseId. The full parameter table on this page comes from the server's own tool schema.
Register the Moodle MCP server in PolicyLayer and add a rule for get_course_completion_status: 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.
get_course_completion_status 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_course_completion_status 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_course_completion_status. 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_course_completion_status is provided by the Moodle MCP server (@falkenslab/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