restore_course

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/restore-course.md

WHAT IT DOES

What restore_course does on Moodle

AI agents use restore_course to create or update resources in Moodle, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moodle environment.

Parameter	Type	Required	Description
`file`	string	Yes	The backup's absolute local path (.mbz)
`mode`	string	—	Into an existing course: add to it (default) or replace its content
`fullName`	string	—
`sectionId`	integer	—	Merged into a course: every restored activity at the end of this section
`shortName`	string	—
`withUsers`	boolean	—	Restore the participants' data the backup has (default false)
`categoryId`	integer	—	For a new course: its category
`intoCourseId`	integer	—	An existing course to restore into; a new course when missing
`afterSectionId`	integer	—	Merged into a course: the backup's sections as new sections after this one

Parameters from the server's own tool schema.

RISK

Why restore_course is rated Medium

An AI agent can call restore_course faster than any human can review: one bad instruction and it creates or modifies resources in Moodle by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (file) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restore_course 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 restore_course, this is the rule to start with:

restore_course Rate-limited

restore_course stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore_course": {
      "limits": [
        {
          "counter": "restore_course_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every restore_course call is checked against it from then on.

FAQ

Questions about restore_course

What does the restore_course tool do? +

Restore a .mbz backup through Moodle's restore wizard: into a new course in a category (no intoCourseId), or into an existing course, adding to its content (mode merge, the default) or replacing it (replace deletes the course's content first). Merged into a course, sectionId puts every restored activity at the end of that section, and afterSectionId the backup's sections as new ones after that one; the result names the new sections and activities, and warnings what was left broken (restrictions or links to what wasn't restored) for the person to fix. A new course takes the backup's names unless fullName and shortName are given. A backup from a newer Moodle, or with activity types this site doesn't offer, is refused. It can take minutes: Moodle does it in steps, and waits up to ten. Changes Moodle, and replace can't be undone: confirm with the person first. It is categorised as a Write tool in the Moodle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does restore_course accept? +

restore_course accepts 9 parameters: file, mode, fullName, sectionId, shortName, withUsers, categoryId, intoCourseId, afterSectionId. Required: file. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on restore_course? +

Register the Moodle MCP server in PolicyLayer and add a rule for restore_course: 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.

What risk level is restore_course? +

restore_course is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore_course? +

Yes. Add a rate_limit block to the restore_course 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 restore_course completely? +

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

restore_course 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.

KEEP EXPLORING

More on Moodle, and thousands of servers like it.

This server

All 233 Moodle tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →