list_announcements
AI agents call list_announcements 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.
Despite the empty description, the naming convention and context of sibling tools strongly suggest this retrieves or queries announcement data from Canvas LMS without side effects. Listing announcements is a standard read operation. Confidence is moderate due to lack of explicit description, but the pattern is clear. This presents minimal security risk as it only exposes existing data.
From the tool's definition Tool name is 'list_announcements' which follows the pattern of other read-only tools on this server (list_assignments, get_assignment, get_course, etc.). The 'list' prefix indicates retrieval without modification.
Attacks that exploit this kind of access
list_announcements. 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_announcements: 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_announcements 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_announcements 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_announcements. 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_announcements 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 →