allocate_workshop_randomly

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 71 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-randomly.md

WHAT IT DOES

What allocate_workshop_randomly does on Moodle

AI agents use allocate_workshop_randomly 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
`workshopId`	integer	Yes	The workshop's id (course module id)
`keepCurrent`	boolean	—	Keep the allocations there are (default); false removes them first, never graded ones
`perReviewer`	integer	—	Reviews each reviewer does
`perSubmission`	integer	—	Reviews each submission gets; or perReviewer
`selfAssessment`	boolean	—	Add each author's self-assessment, where the workshop allows it
`excludeSameGroup`	boolean	—	No reviews by peers of the same group (visible groups mode only)
`withoutSubmission`	boolean	—	Reviewers without a submission of their own too; off by default

Parameters from the server's own tool schema.

RISK

Why allocate_workshop_randomly is rated Medium

An AI agent can call allocate_workshop_randomly 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

allocate_workshop_randomly Rate-limited

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

FAQ

Questions about allocate_workshop_randomly

What does the allocate_workshop_randomly tool do? +

Allocate submissions to reviewers at random, as the workshop's random allocation does: perSubmission reviews for each submission, or perReviewer for each reviewer; keeping the current allocations unless keepCurrent is false (graded ones are never removed), among reviewers with a submission unless withoutSubmission, with self-assessments if asked, without peers of the same group if asked. Returns how many were added and removed, Moodle's report and its problems (not enough reviewers…), and the allocation afterwards. Gives participants 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_randomly accept? +

allocate_workshop_randomly accepts 7 parameters: workshopId, keepCurrent, perReviewer, perSubmission, selfAssessment, excludeSameGroup, withoutSubmission. 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_randomly? +

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

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

Can I rate-limit allocate_workshop_randomly? +

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

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

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