Get all student submissions for a specific assignment filtered by section
AI agents call list-section-submissions to retrieve information from Canvas MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries submission data for reporting or review purposes. It has no side effects, does not modify student records, does not execute operations, and does not delete data. It is a straightforward read operation on existing Canvas LMS course data.
From the tool's definition Tool name is 'list-section-submissions' and description states 'Get all student submissions for a specific assignment filtered by section' — uses the verb 'Get' indicating data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access list-section-submissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Canvas MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-section-submissions:
{
"version": "1",
"default": "deny",
"tools": {
"list-section-submissions": {}
}
}list-section-submissions 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 all student submissions for a specific assignment filtered by section. It is categorised as a Read tool in the Canvas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Canvas MCP Server MCP server in PolicyLayer and add a rule for list-section-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 Canvas MCP Server. Nothing to install.
list-section-submissions 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 list-section-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.
Set action: deny in the PolicyLayer policy for list-section-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.
list-section-submissions is provided by the Canvas MCP Server MCP server (r-huijts/canvas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Canvas MCP Server, 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.
50 Canvas MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.