List discussion topics for a course (title, message preview, last reply time). Requires course_id.
AI agents call list_discussions to retrieve information from PokeCanvas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns discussion topic information from Canvas LMS without creating, modifying, deleting, or executing any operations. It retrieves metadata about discussions (title, preview, timestamps) but does not change state. The blast radius of misuse is minimal—an attacker could enumerate discussions but cannot alter grades, modify course content, or access sensitive files.
From the tool's definition Tool name 'list_discussions' and description 'List discussion topics for a course (title, message preview, last reply time)' indicate retrieval of existing data with no modification capability.
Attacks that exploit this kind of access
List discussion topics for a course (title, message preview, last reply time). Requires course_id. It is categorised as a Read tool in the PokeCanvas MCP Server, which means it retrieves data without modifying state.
Register the PokeCanvas 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 PokeCanvas. 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 PokeCanvas MCP server (jackulau/pokecanvas). 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 →