list_potential_users

Find users the person may enrol in a course by manual enrolment, as the "Enrol users" dialog does: matching search in their name or the identity fields the site shows (up to 100 when empty). People as aliases when the server pseudonymizes, never their emails. Enrol them with enrol_users.

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/list-potential-users.md

WHAT IT DOES

What list_potential_users does on Moodle

AI agents call list_potential_users 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
`search`	string	—	Part of a name, an email, an ID number…
`courseId`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why list_potential_users is rated Low

Even though list_potential_users 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

RECOMMENDED RULE

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

list_potential_users Allowed

list_potential_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_potential_users": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every list_potential_users call is checked against it from then on.

FAQ

Questions about list_potential_users

What does the list_potential_users tool do? +

What parameters does list_potential_users accept? +

list_potential_users accepts 2 parameters: search, courseId. Required: courseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_potential_users? +

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

list_potential_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_potential_users? +

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

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

list_potential_users 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →