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.
AI agents call crow_workspace_dir to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a lookup/query function that retrieves workspace path information. It has no side effects, cannot modify data, and does not execute code or commands. The low severity reflects that path information alone poses minimal risk, though confidence is high because the description clearly indicates read-only retrieval.
From the tool's definition Tool description states it 'Returns the absolute filesystem workspace path' and 'Returns the storage prefix'. The verb 'Returns' indicates data retrieval with no modifications.
Documented attack patterns abuse exactly the kind of access crow_workspace_dir gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_workspace_dir:
{
"version": "1",
"default": "deny",
"tools": {
"crow_workspace_dir": {}
}
} crow_workspace_dir is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
crow_workspace_dir 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 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.
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.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.