canvas_get_todo
AI agents call canvas_get_todo 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.
Based on naming convention and server context, this tool retrieves to-do items from Canvas LMS (student's todo list or pending tasks). No side effects are described or implied. The 'get' prefix strongly indicates a read-only query operation. Confidence is slightly reduced due to empty description, but sibling context and naming convention justify 'Read' category with low severity.
From the tool's definition Tool name 'canvas_get_todo' indicates retrieval/query operation. Description is empty, but sibling tools on this server (canvas_get_announcements, canvas_get_assignments, canvas_get_grades, canvas_get_discussions) all follow the 'canvas_get_*' naming pattern…
Attacks that exploit this kind of access
canvas_get_todo. 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_get_todo: 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_get_todo 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_get_todo 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_get_todo. 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_get_todo 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 →