Get submission and grading status for a specific assignment by its ID
AI agents call get_assignment_status to retrieve information from Moodle-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries assignment submission and grading information from the Moodle LMS and returns status data. It performs a read-only retrieval operation with no side effects, data modification, or destructive action. The blast radius of misuse is minimal—an AI agent could retrieve status information it shouldn't access, but cannot alter grades, submissions, or course data. Classified as Read with low severity.
From the tool's definition Tool retrieves 'submission and grading status' for an assignment, explicitly a query operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_assignment_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moodle-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_assignment_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_assignment_status": {}
}
} get_assignment_status 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 submission and grading status for a specific assignment by its ID. It is categorised as a Read tool in the Moodle-MCP MCP Server, which means it retrieves data without modifying state.
Register the Moodle- MCP server in PolicyLayer and add a rule for get_assignment_status: 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. Nothing to install.
get_assignment_status 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 get_assignment_status 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 get_assignment_status. 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.
get_assignment_status is provided by the Moodle- MCP server (loyaniu/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moodle-MCP, 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.
24 Moodle-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.