This record as markdown: /tools/cowork-bench/list-databases.md
What list_databases does on Cowork Bench
AI agents call list_databases 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 list_databases is rated Low
This tool retrieves or lists information about available databases without creating, modifying, deleting, executing, or moving data. It is a passive information retrieval operation with minimal security impact, making it a Read category tool with low severity.
From the tool's definition Tool name 'list_databases' and description 'List all available databases in hr1c' indicate a query/retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs list_databases 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 list_databases, this is the rule to start with:
list_databases 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 list_databases call is checked against it from then on.
Questions about list_databases
List all available databases in hr1c. 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 list_databases: 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.
list_databases 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 list_databases 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 list_databases. 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.
list_databases 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