allocate_workshop_reviewer

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/allocate-workshop-reviewer.md

WHAT IT DOES

What allocate_workshop_reviewer does on Moodle

AI agents use allocate_workshop_reviewer 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
`author`	string	—	The submission's author's alias, when the server pseudonymizes
`authorId`	integer	—	The submission's author's user id, when the server shows names
`reviewer`	string	—	The reviewer's alias, when the server pseudonymizes
`reviewerId`	integer	—	The reviewer's user id, when the server shows names
`workshopId`	integer	Yes	The workshop's id (course module id)
`submissionId`	integer	—	The submission, as get_workshop_allocation gives it; or its author

Parameters from the server's own tool schema.

RISK

Why allocate_workshop_reviewer is rated Medium

An AI agent can call allocate_workshop_reviewer 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

allocate_workshop_reviewer Rate-limited

allocate_workshop_reviewer 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": {
    "allocate_workshop_reviewer": {
      "limits": [
        {
          "counter": "allocate_workshop_reviewer_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 allocate_workshop_reviewer call is checked against it from then on.

FAQ

Questions about allocate_workshop_reviewer

What does the allocate_workshop_reviewer tool do? +

Allocate a reviewer to a submission, as the manual allocation page's "Add reviewer" does, in any phase. The submission by its id or its author, the reviewer one get_workshop_allocation lists as a potential reviewer (aliases when the server pseudonymizes). A reviewer already allocated is left as is. Returns the submission's reviewers afterwards. The reviewer is given work: 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 allocate_workshop_reviewer accept? +

allocate_workshop_reviewer accepts 6 parameters: author, authorId, reviewer, reviewerId, workshopId, submissionId. Required: workshopId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on allocate_workshop_reviewer? +

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

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

Can I rate-limit allocate_workshop_reviewer? +

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

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

allocate_workshop_reviewer 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 →