list_glossary_entries
Read a glossary's entries in its order: concept, definition (HTML), aliases, categories, author (an alias when the server pseudonymizes), whether approved, attachments. What the person sees: approved entries and their own waiting; pending gives those waiting for approval, for a teacher. By letter...
This record as markdown: /tools/falkenslab-moodle-mcp/list-glossary-entries.md
What list_glossary_entries does on Moodle
AI agents call list_glossary_entries to retrieve information from Moodle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | How many entries (30 by default, up to 200) |
letter | string | — | Only concepts starting with this letter |
offset | integer | — | How many entries to skip first (0 by default) |
search | string | — | Words in concepts, aliases or definitions |
pending | boolean | — | The entries waiting for approval instead (a teacher's) |
glossaryId | integer | Yes | The glossary's id (course module id), as get_course_structure gives it |
Parameters from the server's own tool schema.
Why list_glossary_entries is rated Low
Even though list_glossary_entries only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_glossary_entries 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 list_glossary_entries, this is the rule to start with:
list_glossary_entries is read-only, so it stays allowed. 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 list_glossary_entries call is checked against it from then on.
Questions about list_glossary_entries
Read a glossary's entries in its order: concept, definition (HTML), aliases, categories, author (an alias when the server pseudonymizes), whether approved, attachments. What the person sees: approved entries and their own waiting; pending gives those waiting for approval, for a teacher. By letter, or a search of concepts, aliases and definitions. A page at a time: limit entries (30 by default) after skipping offset; more says whether there are others. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
list_glossary_entries accepts 6 parameters: limit, letter, offset, search, pending, glossaryId. Required: glossaryId. 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 list_glossary_entries: 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.
list_glossary_entries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_glossary_entries 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 list_glossary_entries. 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.
list_glossary_entries 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