canvas_list_modules

List all modules in a course

SERVERCowork Bench SOURCE0717376/cowork_bench

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-bench/canvas-list-modules.md

WHAT IT DOES

What canvas_list_modules does on Cowork Bench

AI agents call canvas_list_modules 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.

RISK

Why canvas_list_modules is rated Low

This tool performs a straightforward data retrieval operation ('list') on course modules. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. It is clearly a Read category tool with low severity due to its informational nature and limited blast radius if misused by an AI agent.

From the tool's definition Tool name 'canvas_list_modules' and description 'List all modules in a course' indicate a read-only query operation that retrieves course module information without modifying, deleting, or executing any operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs canvas_list_modules 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_list_modules, this is the rule to start with:

canvas_list_modules Allowed

canvas_list_modules is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "canvas_list_modules": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every canvas_list_modules call is checked against it from then on.

FAQ

Questions about canvas_list_modules

What does the canvas_list_modules tool do? +

List all modules in a course. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on canvas_list_modules? +

Register the Cowork Bench MCP server in PolicyLayer and add a rule for canvas_list_modules: 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.

What risk level is canvas_list_modules? +

canvas_list_modules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit canvas_list_modules? +

Yes. Add a rate_limit block to the canvas_list_modules 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.

How do I block canvas_list_modules completely? +

Set action: deny in the PolicyLayer policy for canvas_list_modules. 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.

What MCP server provides canvas_list_modules? +

canvas_list_modules 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.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →