export_database_entries

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/export-database-entries.md

WHAT IT DOES

What export_database_entries does on Moodle

AI agents use export_database_entries to create or update resources in Moodle, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moodle environment.

Parameter	Type	Required	Description
`file`	string	Yes	An absolute local path for the CSV (replaced if it's there)
`times`	boolean	—
`approval`	boolean	—
`databaseId`	integer	Yes	The database's id (course module id), as get_course_structure gives it
`userDetails`	boolean	—	The authors' full name, username and email

Parameters from the server's own tool schema.

RISK

Why export_database_entries is rated Medium

An AI agent can call export_database_entries faster than any human can review: one bad instruction and it creates or modifies resources in Moodle by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (file) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_database_entries safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Moodle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_database_entries, this is the rule to start with:

export_database_entries Rate-limited

export_database_entries stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_database_entries": {
      "limits": [
        {
          "counter": "export_database_entries_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every export_database_entries call is checked against it from then on.

FAQ

Questions about export_database_entries

What does the export_database_entries tool do? +

Save a database activity's entries to a local CSV file, as its "Export entries" does: a column per field (images and files aren't in it), with the authors' details, times and approval if asked. Every entry of the person's group. The file holds what participants wrote as is: only with names in clear (the server's student data level). It is categorised as a Write tool in the Moodle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does export_database_entries accept? +

export_database_entries accepts 5 parameters: file, times, approval, databaseId, userDetails. Required: file, databaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on export_database_entries? +

Register the Moodle MCP server in PolicyLayer and add a rule for export_database_entries: 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 export_database_entries? +

export_database_entries is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_database_entries? +

Yes. Add a rate_limit block to the export_database_entries 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 export_database_entries completely? +

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

export_database_entries 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.

KEEP EXPLORING

More on Moodle, and thousands of servers like it.

This server

All 233 Moodle tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →