Add or update a member of a project space. Upsert: if the contact already has an active membership, the role/capabilities are updated. Requires manage_members capability on the project. Pass contact_id=null to set the local-user owner (typically only used at project create time).
AI agents use crow_add_member 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 modifies project membership data and user roles/capabilities. While reversible (members can be removed or role-changed later), it grants significant organizational access and could alter project permissions if misused by an AI agent.
From the tool's definition 'Add or update a member of a project space. Upsert' — creates or modifies membership records reversibly. 'Requires manage_members capability on the project' indicates access control.
Documented attack patterns abuse exactly the kind of access crow_add_member 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_add_member:
{
"version": "1",
"default": "deny",
"tools": {
"crow_add_member": {
"limits": [
{
"counter": "crow_add_member_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crow_add_member 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.
Add or update a member of a project space. Upsert: if the contact already has an active membership, the role/capabilities are updated. Requires manage_members capability on the project. Pass contact_id=null to set the local-user owner (typically only used at project create time). 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_add_member: 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_add_member 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_add_member 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_add_member. 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_add_member 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.