Low Risk

get_submissions

Obtiene las entregas de tareas en el curso configurado

How to control get_submissions ↓

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

Low Risk

This tool queries and retrieves submission data from a Moodle course. It performs a read-only operation on student assignments/tasks, returning information about submitted work. There are no side effects, no data modification, and no irreversible actions.

From the tool's definition Tool name 'get_submissions' and description 'Obtiene las entregas de tareas en el curso configurado' (Gets task submissions in the configured course) indicate retrieval of existing submission data with no modification or deletion.

Documented attack patterns abuse exactly the kind of access get_submissions gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_submissions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_submissions": {}
  }
}

get_submissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Moodle MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_submissions tool do? +

Obtiene las entregas de tareas en el curso configurado. It is categorised as a Read tool in the Moodle MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_submissions? +

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

What risk level is get_submissions? +

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

Can I rate-limit get_submissions? +

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

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

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

Enforce policy on every Moodle MCP Server tool call.

Deterministic rules across all 8 Moodle MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 Moodle MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.