AI agents use archive_conversation 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.
Archiving is a Write operation because it modifies data state reversibly without deleting or destroying the underlying data. While archiving removes conversations from active view, the action is generally undoable in LMS systems. Severity is medium because misuse could hide important communications from instructors or students, but no data is permanently lost and the impact is localized to a specific conversation.
From the tool's definition Tool name 'archive_conversation' and description 'Archive a conversation' indicate a state-change operation that modifies conversation metadata or status, making it reversible (conversations can typically be unarchived).
Documented attack patterns abuse exactly the kind of access archive_conversation 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 archive_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"archive_conversation": {
"limits": [
{
"counter": "archive_conversation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_conversation 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.
Archive a conversation. 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 archive_conversation: 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.
archive_conversation 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 archive_conversation 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 archive_conversation. 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.
archive_conversation is provided by the Canvas MCP Server MCP server (plyght/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.
30 Canvas MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.