canvas_list_courses
AI agents call canvas_list_courses to retrieve information from Canvas LMS 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 course information without side effects. The sibling tools on the server include write operations (canvas_create_*), destructive operations (canvas_delete_*), and other reads (canvas_get_*), but this specific tool follows the 'list' pattern which is a standard read operation. Even with an empty description, the name and server context make the classification clear.
From the tool's definition Tool name 'canvas_list_courses' indicates listing/querying courses. The server description confirms it 'retrieve[s]' courses from the student account. No modification, deletion, or execution semantics are present.
Attacks that exploit this kind of access
canvas_list_courses. It is categorised as a Read tool in the Canvas LMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Canvas LMS MCP Server MCP server in PolicyLayer and add a rule for canvas_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 LMS MCP Server. Nothing to install.
canvas_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 canvas_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 canvas_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.
canvas_list_courses is provided by the Canvas LMS MCP Server MCP server (sweeden-ttu/canvas-lms-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 →