This record as markdown: /tools/kh0pper-crow/crow-project-stats.md
What crow_project_stats does on Crow
AI agents call crow_project_stats 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.
Why crow_project_stats is rated Low
This tool only queries and returns aggregate information (statistics) about a project database. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal: an AI agent could retrieve statistical summaries but cannot modify data, trigger external actions, or cause harm. Classified as Read with low severity.
From the tool's definition Tool description states it 'Get statistics about the project database' — a retrieval operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
The rule that runs crow_project_stats 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_project_stats, this is the rule to start with:
crow_project_stats 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 Crow, apply this rule, and every crow_project_stats call is checked against it from then on.
Questions about crow_project_stats
Get statistics about the project database. 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_project_stats: 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_project_stats 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_project_stats 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_project_stats. 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_project_stats 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue