list_discussions
AI agents call list_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.
The 'list' prefix and context of an academic LMS server indicate a retrieval operation. The tool appears designed to query and display discussions, which aligns with the read-only pattern of sibling tools. No side effects, modifications, deletions, or financial operations are implied. Severity is low because listing discussions poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'list_discussions' with no description provided. Based on sibling tools on this server (find_assignments_by_due_date, get_all_upcoming_work, get_assignment, get_course, get_discussion_entries, get_rubric, get_submission, get_upcoming_assignments,…
Attacks that exploit this kind of access
list_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 list_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.
list_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 list_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 list_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.
list_discussions is provided by the Canvas LMS MCP Server MCP server (pranavkarthik10/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 →