schedule_workshop_allocation

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/schedule-workshop-allocation.md

WHAT IT DOES

What schedule_workshop_allocation does on Moodle

AI agents use schedule_workshop_allocation 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
`enabled`	boolean	Yes
`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 schedule_workshop_allocation is rated Medium

An AI agent can call schedule_workshop_allocation 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 schedule_workshop_allocation 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 schedule_workshop_allocation, this is the rule to start with:

schedule_workshop_allocation Rate-limited

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

FAQ

Questions about schedule_workshop_allocation

What does the schedule_workshop_allocation tool do? +

Turn the workshop's scheduled allocation on or off: when on, Moodle allocates at random by itself at the end of the submission phase (once its submissions deadline passes), with the random allocation's settings given here (those left out keep what the form has). Returns the settings and Moodle's status of it (without a submissions deadline it never runs). 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 schedule_workshop_allocation accept? +

schedule_workshop_allocation accepts 8 parameters: enabled, workshopId, keepCurrent, perReviewer, perSubmission, selfAssessment, excludeSameGroup, withoutSubmission. Required: enabled, workshopId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on schedule_workshop_allocation? +

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

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

Can I rate-limit schedule_workshop_allocation? +

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

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

schedule_workshop_allocation 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

sms_schedule on Twilio SMS MCP Server → The MCP Attack Database →

Guides

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