canvas_get_discussions
AI agents call canvas_get_discussions 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 discussion data from Canvas LMS with no side effects. The empty description lowers confidence slightly, but the tool name and server context clearly indicate a read operation. The data returned is limited to the user's own student account, constraining blast radius. Classified as Read with low severity.
From the tool's definition Tool name 'canvas_get_discussions' and server description stating it 'retrieve[s]...discussions' from student account; no mention of modification or deletion.
Attacks that exploit this kind of access
canvas_get_discussions. 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_discussions: 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_discussions 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_discussions 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_discussions. 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_discussions 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 →