crow_remove_member
Soft-revoke a member from a project space (sets revoked_at; does not delete the row). Requires manage_members. Cannot remove the local owner.
This record as markdown: /tools/kh0pper-crow/crow-remove-member.md
What crow_remove_member does on Crow
AI agents use crow_remove_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.
Why crow_remove_member is rated Medium
The tool revokes a member's access by setting a revoked_at timestamp rather than deleting the record, making it a reversible write operation. However, the blast radius is high because revoking a member removes their access to the project space, which could disrupt collaboration and lock out legitimate users if misused.
From the tool's definition Soft-revoke a member from a project space (sets revoked_at; does not delete the row)
Attacks that exploit this kind of access
The rule that runs crow_remove_member 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_remove_member, this is the rule to start with:
crow_remove_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_remove_member call is checked against it from then on.
Questions about crow_remove_member
Soft-revoke a member from a project space (sets revoked_at; does not delete the row). Requires manage_members. Cannot remove the local owner. 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_remove_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_remove_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_remove_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_remove_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_remove_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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue