get_submission_status
AI agents call get_submission_status to retrieve information from Moodle Student MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves submission status information for a student's own submissions in Moodle. This is a read operation that queries existing data without side effects. The server is explicitly read-only and uses a personal token for authenticated access. Even without an explicit description, the naming convention and server context make it clear this retrieves rather than modifies data.
From the tool's definition Tool is part of Moodle Student MCP described as 'read-only querying' with sibling tools like get_grades, list_assignments, get_course_contents that all retrieve data. Tool name get_submission_status indicates retrieval of submission metadata.
Attacks that exploit this kind of access
get_submission_status. It is categorised as a Read tool in the Moodle Student MCP MCP Server, which means it retrieves data without modifying state.
Register the Moodle Student MCP server in PolicyLayer and add a rule for get_submission_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 Student MCP. Nothing to install.
get_submission_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_submission_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_submission_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_submission_status is provided by the Moodle Student MCP server (tcpassos/moodle-student-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →