AI agents call listar_mis_cursos to retrieve information from Moodle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves enrollment information for a user without modifying any data or triggering external operations. It is a straightforward data retrieval operation. Severity is low because listing course enrollments poses minimal security risk even if misused by an AI agent—the worst outcome would be accessing information the querying user should already have visibility to.
From the tool's definition Tool name and description indicate 'List courses where a user is enrolled' - a query operation with no side effects. No creation, modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
List courses where a user is enrolled. Accepts userid (ej: obtain from obtener_info_sitio for the bot, or pass an alumno_id-mapped Moodle userid). It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
Register the Moodle MCP server in PolicyLayer and add a rule for listar_mis_cursos: 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.
listar_mis_cursos 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 listar_mis_cursos 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 listar_mis_cursos. 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.
listar_mis_cursos is provided by the Moodle MCP server (marcosnahuel/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →