delete_workshop_example
Delete an example submission with its assessments (the reference one and participants' practice ones). Can't be undone: confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/delete-workshop-example.md
What delete_workshop_example does on Moodle
AI agents call delete_workshop_example to permanently remove resources in Moodle, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
exampleId | integer | Yes | As list_workshop_examples gives it |
workshopId | integer | Yes | The workshop's id (course module id) |
Parameters from the server's own tool schema.
Why delete_workshop_example is rated Critical
An AI agent that decides to call delete_workshop_example doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Moodle is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_workshop_example 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 delete_workshop_example, this is the rule to start with:
delete_workshop_example is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every delete_workshop_example call is checked against it from then on.
Questions about delete_workshop_example
Delete an example submission with its assessments (the reference one and participants' practice ones). Can't be undone: confirm with the person first. It is categorised as a Destructive tool in the Moodle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_workshop_example accepts 2 parameters: exampleId, workshopId. Required: exampleId, workshopId. The full parameter table on this page comes from the server's own tool schema.
Register the Moodle MCP server in PolicyLayer and add a rule for delete_workshop_example: 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.
delete_workshop_example is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_workshop_example 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.
Set action: deny in the PolicyLayer policy for delete_workshop_example. 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.
delete_workshop_example 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.
More on Moodle, and thousands of servers like it.
Across the catalogue