list_sites

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_sites does on Moodle

AI agents call list_sites 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.

RISK

Why list_sites is rated Low

Even though list_sites 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_sites 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_sites, this is the rule to start with:

list_sites Allowed

list_sites 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_sites": {}
  }
}

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_sites call is checked against it from then on.

FAQ

Questions about list_sites

What does the list_sites tool do? +

List the Moodle sites this server knows, by name: their URL, which one is active (every other tool works on it) and whether each comes from the person's configuration or was added at run time. Switch with use_site. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_sites? +

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

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

Can I rate-limit list_sites? +

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

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

list_sites 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 →