crow_workspace_dir

Returns the absolute filesystem workspace path for a project space. Bots and agents call this before writing artifacts. Returns the storage prefix (MinIO key prefix) too.

SERVERCrow SOURCEkh0pper/crow

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/kh0pper-crow/crow-workspace-dir.md

WHAT IT DOES

What crow_workspace_dir does on Crow

AI agents call crow_workspace_dir to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why crow_workspace_dir is rated Low

This tool queries and retrieves path and storage information for a project workspace. It has no side effects: it does not create, modify, delete, or execute anything. While the returned paths could theoretically be used by other tools to perform destructive actions, this tool itself merely reads and returns existing information.

From the tool's definition Tool description states it "Returns the absolute filesystem workspace path" and "Returns the storage prefix" — both read operations that retrieve configuration/path information without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_workspace_dir safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_workspace_dir, this is the rule to start with:

crow_workspace_dir Allowed

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

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

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

FAQ

Questions about crow_workspace_dir

What does the crow_workspace_dir tool do? +

Returns the absolute filesystem workspace path for a project space. Bots and agents call this before writing artifacts. Returns the storage prefix (MinIO key prefix) too. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_workspace_dir? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_workspace_dir: 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 Crow. Nothing to install.

What risk level is crow_workspace_dir? +

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

Can I rate-limit crow_workspace_dir? +

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

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

crow_workspace_dir is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

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