list_workspace
List files in the agent workspace. Shows folder tree with file sizes and dates.
This record as markdown: /tools/io-github-homenshum-nodebench/list-workspace.md
What list_workspace does on Nodebench
AI agents call list_workspace to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workspace is rated Low
This tool queries and displays file system information (names, sizes, dates) without modifying, executing, or deleting any data. It is a straightforward directory listing utility with no side effects, fitting the Read category.
From the tool's definition Tool name 'list_workspace' and description 'List files in the agent workspace. Shows folder tree with file sizes and dates.' indicate a read-only operation that retrieves directory and file metadata.
Attacks that exploit this kind of access
The rule that runs list_workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workspace, this is the rule to start with:
list_workspace 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 Nodebench, apply this rule, and every list_workspace call is checked against it from then on.
Questions about list_workspace
List files in the agent workspace. Shows folder tree with file sizes and dates. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for list_workspace: 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 Nodebench. Nothing to install.
list_workspace 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_workspace 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_workspace. 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_workspace is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue