Get available Moodle versions in the developer documentation
AI agents call get_versions to retrieve information from Moodle Developer Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists available Moodle versions from the documentation. It performs no modifications, deletions, code execution, or financial operations. It is purely informational—a read-only query of version metadata. The blast radius of misuse is minimal, as it only exposes publicly available version information.
From the tool's definition Tool name 'get_versions' and description 'Get available Moodle versions in the developer documentation' indicate a retrieval operation that queries metadata about available documentation versions without modifying any data.
Attacks that exploit this kind of access
Get available Moodle versions in the developer documentation. It is categorised as a Read tool in the Moodle Developer Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Moodle Developer Documentation MCP Server MCP server in PolicyLayer and add a rule for get_versions: 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 Developer Documentation MCP Server. Nothing to install.
get_versions 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_versions 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_versions. 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_versions is provided by the Moodle Developer Documentation MCP Server MCP server (khairu-aqsara/moodle_dev_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 →