Get sections and modules for a specific course by its ID
AI agents call get_course_content to retrieve information from Moodle-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves course content metadata (sections and modules) from the Moodle LMS. It performs a read-only operation with no side effects, data modification, code execution, or irreversible actions. The small blast radius and low risk of misuse justify a 'low' severity classification.
From the tool's definition 'Get sections and modules for a specific course by its ID' - retrieves course structure information without modification or execution
Documented attack patterns abuse exactly the kind of access get_course_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_course_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_course_content": {}
}
} get_course_content is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get sections and modules for a specific course by its ID. It is categorised as a Read tool in the Moodle-MCP MCP Server, which means it retrieves data without modifying state.
Register the Moodle- MCP server in PolicyLayer and add a rule for get_course_content: 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-MCP. Nothing to install.
get_course_content 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 get_course_content 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 get_course_content. 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.
get_course_content is provided by the Moodle- MCP server (loyaniu/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moodle-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Moodle-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.