Create a new project to organize sources, notes, and data backends under.
AI agents use crow_create_project to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
This tool creates a new project entity in the project management system. This is a Write operation as it adds data reversibly—projects can be modified or deleted later. There is no indication of destructive, financial, or code execution capabilities. The blast radius is low as creating a project in a management system is a standard, reversible operation with minimal risk of harm.
From the tool's definition Tool description states 'Create a new project' which is a clear create operation that adds new data to the system.
Documented attack patterns abuse exactly the kind of access crow_create_project 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_create_project:
{
"version": "1",
"default": "deny",
"tools": {
"crow_create_project": {
"limits": [
{
"counter": "crow_create_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crow_create_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new project to organize sources, notes, and data backends under. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_create_project: 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_create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crow_create_project 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_create_project. 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_create_project 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.