New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_course_logs

Read a course's logs, newest first, as its logs report lists them: by a user (an alias when the server pseudonymizes), an activity, a kind of action and a time span, a page at a time: limit entries (50 by default) after skipping offset; more says whether there are others. Each entry: when, who, w...

SERVERMoodle SOURCE@falkenslab/moodle-mcp
Low RISK CLASS
Category Read
Parameters 101 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/get-course-logs.md

What get_course_logs does on Moodle

AI agents call get_course_logs to retrieve information from Moodle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
from string — ISO 8601
user string — The participant's alias, as the reading tools give it when the server pseudonymizes
limit integer — How many entries (50 by default)
until string — ISO 8601
action string —
offset integer — How many entries to skip first, newest first (0 by default)
userId integer — The participant's user id, when the server shows names
courseId integer Yes
activityId integer —
includeDescriptions boolean — Also each entry's description, Moodle's sentence about it (longer; default false)

Parameters from the server's own tool schema.

Why get_course_logs is rated Low

Even though get_course_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (10 properties)

Questions about get_course_logs

What does the get_course_logs tool do? +

Read a course's logs, newest first, as its logs report lists them: by a user (an alias when the server pseudonymizes), an activity, a kind of action and a time span, a page at a time: limit entries (50 by default) after skipping offset; more says whether there are others. Each entry: when, who, who it was about, where, what happened (Moodle's longer description only with includeDescriptions). Never IP addresses. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.

What parameters does get_course_logs accept? +

get_course_logs accepts 10 parameters: from, user, limit, until, action, offset, userId, courseId, activityId, includeDescriptions. Required: courseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_course_logs? +

Register the Moodle MCP server in PolicyLayer and add a rule for get_course_logs: 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. Nothing to install.

What risk level is get_course_logs? +

get_course_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_course_logs? +

Yes. Add a rate_limit block to the get_course_logs 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.

How do I block get_course_logs completely? +

Set action: deny in the PolicyLayer policy for get_course_logs. 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.

What MCP server provides get_course_logs? +

get_course_logs is provided by the Moodle MCP server (@falkenslab/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Moodle, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Moodle's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.