AI agents call summary to retrieve information from Moodle Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries course data (summary aggregation), placing it in the Read category. Severity is medium rather than low because the tool returns comprehensive course data which could include sensitive educational information (grades, assignments, student progress), making it moderately risky if exposed to an untrusted agent.
From the tool's definition Tool name 'summary' and description 'Get full summary of all course data' indicates a data retrieval operation that aggregates course information without modifying, executing operations, or deleting data.
Documented attack patterns abuse exactly the kind of access summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for summary:
{
"version": "1",
"default": "deny",
"tools": {
"summary": {}
}
}summary 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 full summary of all course data. It is categorised as a Read tool in the Moodle Connector MCP Server, which means it retrieves data without modifying state.
Register the Moodle Connector MCP server in PolicyLayer and add a rule for summary: 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 Connector. Nothing to install.
summary 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 summary 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 summary. 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.
summary is provided by the Moodle Connector MCP server (jabir-srj/moodle-connector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moodle Connector, 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.
8 Moodle Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.