Search Moodle developer documentation for specific topics or APIs
AI agents call search_docs 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 searches and retrieves documentation content—a read-only operation with no side effects. It cannot modify data, execute code, delete resources, or commit financial obligations. The lowest-severity category 'Read' applies.
From the tool's definition Tool name 'search_docs' and description 'Search Moodle developer documentation for specific topics or APIs' indicate a retrieval operation with no data modification or execution capabilities.
Attacks that exploit this kind of access
Search Moodle developer documentation for specific topics or APIs. 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 search_docs: 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.
search_docs 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 search_docs 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 search_docs. 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.
search_docs 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 →