save_workshop_submission

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/save-workshop-submission.md

WHAT IT DOES

What save_workshop_submission does on Moodle

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

Parameter	Type	Required	Description
`embed`	array	—	Absolute local files to embed in the text, which names each by its file name: <img src="shot.png">
`title`	string	—	Its title; a new one needs it
`content`	string	—	Its text (HTML), where the workshop takes online text; no aliases in it
`workshopId`	integer	Yes	The workshop's id (course module id)
`attachments`	array	—	Absolute local paths: they replace the files attached before

Parameters from the server's own tool schema.

RISK

Why save_workshop_submission is rated Medium

An AI agent can call save_workshop_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 signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

save_workshop_submission Rate-limited

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

FAQ

Questions about save_workshop_submission

What does the save_workshop_submission tool do? +

Add the person's submission to a workshop, or change the one they have, through its submission form: title, text (HTML, with local images embedded), attached local files; only what is given changes (a new one needs a title). Moodle takes it in the submission phase, within its dates. Returns the submission. Reviewers will read it: 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 save_workshop_submission accept? +

save_workshop_submission accepts 5 parameters: embed, title, content, workshopId, attachments. Required: workshopId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_workshop_submission? +

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

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

Can I rate-limit save_workshop_submission? +

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

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

save_workshop_submission 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

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

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