create_question
Create one question in a question bank through its type's form, of any type: multichoice, truefalse, shortanswer, numerical, essay, calculated (simple and multichoice too), match, randomsamatch, drag and drop into text (ddwtos), onto an image (ddimageortext), markers (ddmarker), select missing wo...
This record as markdown: /tools/falkenslab-moodle-mcp/create-question.md
What create_question does on Moodle
AI agents use create_question 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 |
|---|---|---|---|
name | string | Yes | |
sets | integer | — | Calculated types: how many sets of values (10 by default) |
text | string | Yes | The question text (HTML) |
type | string | Yes | |
drags | array | — | ddimageortext: the draggable items |
drops | array | — | ddimageortext, ddmarker: where the items or markers go |
image | string | — | ddimageortext, ddmarker: the background image, an absolute local path |
items | array | — | ordering: the items, in the right order |
pairs | array | — | match, ddmatch: each question and its answer; an answer without a question is a distractor |
bankId | integer | Yes | The bank's id (a course module id), as list_question_banks gives it |
choose | integer | — | randomsamatch: how many short-answer questions of the category it draws |
fields | object | — | Any other field of the type's form, by name |
Parameters from the server's own tool schema.
Why create_question is rated Medium
An AI agent can call create_question 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 freeform code/query input (coderunner.testCases[].code) · High parameter count (68 properties)
Attacks that exploit this kind of access
The rule that runs create_question 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 create_question, this is the rule to start with:
create_question 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every create_question call is checked against it from then on.
Questions about create_question
Create one question in a question bank through its type's form, of any type: multichoice, truefalse, shortanswer, numerical, essay, calculated (simple and multichoice too), match, randomsamatch, drag and drop into text (ddwtos), onto an image (ddimageortext), markers (ddmarker), select missing words (gapselect), Cloze (multianswer, its answers in the text), ordering, description, and the plugins coderunner, formulas, gapfill and ddmatch where the site has them. Each type takes its own inputs, checked before Moodle. The text holds the type's places: [[1]] for ddwtos and gapselect, {1:SHORTANSWER:=Paris} for Cloze, [gaps] for gapfill, {wildcards} for calculated. For several, import_questions is faster. Returns the new question's id. Changes the bank: 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.
create_question accepts 12 parameters: name, sets, text, type, drags, drops, image, items, pairs, bankId, choose, fields. Required: name, text, type, bankId. 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 create_question: 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.
create_question is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_question 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 create_question. 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.
create_question 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.
This server
Across the catalogue