List Canvas courses for the authenticated user. Can filter by enrollment state (active, completed, invited, rejected).
AI agents call list_courses 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 course data available to an authenticated user. It is a read-only operation with no side effects, reversible modifications, code execution, data destruction, or financial implications. The filtering capability is a standard query parameter that narrows results without altering state.
From the tool's definition Tool name is 'list_courses' and description states it 'List Canvas courses for the authenticated user' with optional filtering by enrollment state. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
List Canvas courses for the authenticated user. Can filter by enrollment state (active, completed, invited, rejected). 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_courses: 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_courses 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_courses 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_courses. 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_courses is provided by the Canvas MCP Server MCP server (taciturnaxolotl/canvas-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 →