8 tools. 1 can modify or destroy data without limits.
1 write tool that can modify data. Rate limits recommended.
Last updated:
Community server · catalogue entry verified 11/06/2026
1 of Moodle MCP Server's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"provide_feedback": {
"limits": [
{
"counter": "provide_feedback_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"get_assignments": {
"limits": [
{
"counter": "get_assignments_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Free to start. No card required.
The Moodle MCP Server server has 1 write tools including provide_feedback. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Moodle MCP Server.
8 tools across 1 categories: Read. 7 are read-only. 1 can modify, create, or delete data.
Register the Moodle MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 8 Moodle MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Moodle MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.