canvas_get_user
Get a single user by ID (name, email, login_id). Prefer this over canvas_list_account_users when the user_id is already known (e.g. from enrollments).
This record as markdown: /tools/cowork-bench/canvas-get-user.md
What canvas_get_user does on Cowork Bench
AI agents call canvas_get_user to retrieve information from Cowork Bench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why canvas_get_user is rated Low
This tool queries and returns user information without creating, modifying, or deleting data. It is a straightforward read operation that retrieves user details from a system (likely Canvas LMS). The blast radius of misuse is low, as it only exposes user metadata already accessible to authenticated system agents. No state changes occur.
From the tool's definition Tool description states 'Get a single user by ID' and retrieves 'name, email, login_id' — a data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs canvas_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For canvas_get_user, this is the rule to start with:
canvas_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every canvas_get_user call is checked against it from then on.
Questions about canvas_get_user
Get a single user by ID (name, email, login_id). Prefer this over canvas_list_account_users when the user_id is already known (e.g. from enrollments). It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for canvas_get_user: 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 Cowork Bench. Nothing to install.
canvas_get_user 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_get_user 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_get_user. 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_get_user is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
This server
Across the catalogue