list_modules
AI agents call list_modules 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 naming pattern and context of the Canvas LMS MCP server indicate this is a data retrieval tool. The 'list_' prefix and absence of any mutative language strongly suggest querying existing course structure rather than creating, modifying, or deleting data. Confidence is slightly reduced due to the empty description, but the pattern of sibling tools and naming convention provide strong supporting evidence.
From the tool's definition Tool name 'list_modules' with empty description. Based on sibling tools which are predominantly retrieval operations (find_assignments, get_assignment, get_course, list_announcements, etc.), this tool likely lists course modules, a read-only retrieval…
Attacks that exploit this kind of access
list_modules. 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_modules: 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_modules 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_modules 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_modules. 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_modules 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 →