list_allowed_directories

Returns the list of directories that this server is allowed to access.

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/list-allowed-directories.md

WHAT IT DOES

What list_allowed_directories does on Cowork Bench

AI agents call list_allowed_directories 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 list_allowed_directories is rated Low

Even though list_allowed_directories only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_allowed_directories Allowed

list_allowed_directories 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": {
    "list_allowed_directories": {}
  }
}

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 list_allowed_directories call is checked against it from then on.

FAQ

Questions about list_allowed_directories

What does the list_allowed_directories tool do? +

Returns the list of directories that this server is allowed to access. 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 list_allowed_directories? +

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

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

Can I rate-limit list_allowed_directories? +

Yes. Add a rate_limit block to the list_allowed_directories 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 list_allowed_directories completely? +

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

list_allowed_directories 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_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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