Update an assignment. All fields are optional except courseId and assignmentId.
AI agents use update-assignment to create or update resources in Canvas MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Canvas MCP Server environment.
This tool creates or modifies assignment data in Canvas LMS reversibly. It does not delete, does not execute arbitrary code, and does not involve financial transactions. The severity is high because misconfiguration could alter grading rubrics, due dates, or instructional content affecting many students, but the operation is reversible via re-editing.
From the tool's definition Tool name is 'update-assignment' and description states 'Update an assignment' — a clear modification operation. The tool modifies course data reversibly (assignments can be edited again), distinguishing it from destructive deletion.
Documented attack patterns abuse exactly the kind of access update-assignment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Canvas MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update-assignment:
{
"version": "1",
"default": "deny",
"tools": {
"update-assignment": {
"limits": [
{
"counter": "update-assignment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-assignment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an assignment. All fields are optional except courseId and assignmentId. It is categorised as a Write tool in the Canvas MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Canvas MCP Server MCP server in PolicyLayer and add a rule for update-assignment: 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 MCP Server. Nothing to install.
update-assignment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-assignment 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 update-assignment. 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.
update-assignment is provided by the Canvas MCP Server MCP server (r-huijts/canvas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Canvas MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Canvas MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.