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 a specific assignment filtered by section. It performs a read-only operation that does not create, modify, delete, or execute any actions. While it accesses student data which may be sensitive, the tool itself is purely informational with no destructive or executable capabilities.
From the tool's definition Tool name contains 'list' and description states 'Get all student submissions' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
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 (ranver/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 →