# grade_submission

Grade a participant in an assignment, as Moodle's grader does: a grade (simple grading), a rubric's levels or a marking guide's scores per criterion (ids from get_rubric) with remarks, feedback comments (HTML, when the assignment has them on), whether to notify the student, and any other grading field by name in fields. Takes the participant as get_submissions gives them: user (an alias) when the server pseudonymizes, else userId. Works with or without a submission. Returns the grade saved. Changes grades students may see: confirm with the person first.

Agent View of the PolicyLayer registry record for `grade_submission`. HTML page: https://policylayer.com/tools/falkenslab-moodle-mcp/grade-submission

## Facts

- Tool: `grade_submission`
- Server: Moodle (`@falkenslab/moodle-mcp`) — https://policylayer.com/tools/falkenslab-moodle-mcp.md
- Install: `npx -y @falkenslab/moodle-mcp`
- Homepage: https://www.npmjs.com/package/@falkenslab/moodle-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 12 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `user` | string | no | The participant's alias, as the reading tools give it when the server pseudonymizes |
| `grade` | string | no | The grade as text: a number within the range ("7.5"), or a scale item |
| `guide` | object | no | A marking guide's score per criterion: criterion id → score |
| `fields` | object | no | Other grading form fields by name, e.g. a rubric's levels |
| `notify` | boolean | no | Notify the student; Moodle's default when missing |
| `rubric` | object | no | A rubric's level per criterion: criterion id → level id, as get_rubric gives them |
| `userId` | integer | no | The participant's user id, when the server shows names |
| `remarks` | object | no | Remarks per criterion of a rubric or guide: criterion id → text; no aliases |
| `feedback` | string | no | Feedback comments (HTML); no aliases in it, since the student reads it |
| `applyToGroup` | boolean | no | In a group assignment: give the same grade and feedback to the whole group |
| `assignmentId` | integer | yes | The assignment's id (course module id), as list_assignments gives it |
| `feedbackFiles` | array | no | Absolute local paths of feedback files to return to the student |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "grade_submission",
    "arguments": {
      "assignmentId": 0
    }
  }
}
```

## Why grade_submission is rated Medium

An AI agent can call grade_submission 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 signals: High parameter count (13 properties)

## Use case

AI agents use grade_submission 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Moodle:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "grade_submission": {
      "limits": [
        {
          "counter": "grade_submission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Moodle (232)

- `delete_activity` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-activity.md
- `delete_book_chapter` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-book-chapter.md
- `delete_database_entry` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-database-entry.md
- `delete_database_field` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-database-field.md
- `delete_event` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-event.md
- `delete_feedback_item` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-feedback-item.md
- `delete_feedback_template` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-feedback-template.md
- `delete_glossary_entry` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-glossary-entry.md
- `delete_grade_category` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-grade-category.md
- `delete_grade_item` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-grade-item.md
- `delete_group` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-group.md
- `delete_grouping` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-grouping.md
- `delete_lesson_page` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-lesson-page.md
- `delete_post` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-post.md
- `delete_question_category` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-question-category.md
- `delete_questions` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-questions.md
- `delete_section` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-section.md
- `delete_workshop_example` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/delete-workshop-example.md
- `override_workshop_grade` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/override-workshop-grade.md
- `remove_quiz_slot` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/remove-quiz-slot.md
- `remove_site` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/remove-site.md
- `remove_workshop_reviewer` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/remove-workshop-reviewer.md
- `reset_course` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/reset-course.md
- `unenrol_user` — Destructive — https://policylayer.com/tools/falkenslab-moodle-mcp/unenrol-user.md
- `browser_navigate` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/browser-navigate.md
- `browser_wait` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/browser-wait.md
- `enrol_users` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/enrol-users.md
- `grade_forum_user` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/grade-forum-user.md
- `rate` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/rate.md
- `start_quiz_attempt` — Execute — https://policylayer.com/tools/falkenslab-moodle-mcp/start-quiz-attempt.md
- …and 202 more: https://policylayer.com/tools/falkenslab-moodle-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=falkenslab-moodle-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/falkenslab-moodle-mcp