AI agents call canvas_deadlines to retrieve information from Canvas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves deadline data without modifying or executing any operations. It fits the 'Read' category as it queries and returns information about due dates. The low severity reflects minimal risk from misuse—an agent retrieving deadline information cannot cause harm. Confidence is 0.85 rather than higher because the description is incomplete and truncated, leaving some ambiguity about exact functionality.
From the tool's definition Tool name 'canvas_deadlines' and server description indicating 'reading courses, assignments, grades, announcements, discussions' suggest this retrieves deadline information.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Everything due in the next. It is categorised as a Read tool in the Canvas MCP Server, which means it retrieves data without modifying state.
Register the Canvas MCP server in PolicyLayer and add a rule for canvas_deadlines: 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. Nothing to install.
canvas_deadlines 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_deadlines 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_deadlines. 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_deadlines is provided by the Canvas MCP server (tylergibbs1/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 →