crow_list_projects

List all projects with their status, type, and source counts.

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-list-projects.md

WHAT IT DOES

What crow_list_projects does on Crow

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

This tool performs a read-only query of project information. It lists existing projects and their attributes (status, type, source counts) but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an AI agent could view project information but cannot cause irreversible changes or financial impact. This clearly falls under the Read category.

From the tool's definition Tool name 'crow_list_projects' and description 'List all projects with their status, type, and source counts' indicate a retrieval operation that queries project metadata without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

crow_list_projects Allowed

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

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

FAQ

Questions about crow_list_projects

What does the crow_list_projects tool do? +

List all projects with their status, type, and source counts. 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_list_projects? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_list_projects: 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_list_projects? +

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

Can I rate-limit crow_list_projects? +

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

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

crow_list_projects 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

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 →