crow_revoke_access
Revoke a previously shared item or project from a contact. Stops ongoing sync for shared projects. Returns a preview and confirmation token on first call; pass the token back to execute.
This record as markdown: /tools/kh0pper-crow/crow-revoke-access.md
What crow_revoke_access does on Crow
AI agents call crow_revoke_access to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_revoke_access is rated Critical
Revoking access and stopping sync is an irreversible action that removes another contact's ability to access shared projects/items. While a confirmation token mechanism exists, the action itself permanently terminates sharing relationships and ongoing sync, which cannot be undone without re-sharing. This qualifies as Destructive due to the irreversible nature of the access removal.
From the tool's definition Revoke a previously shared item or project from a contact. Stops ongoing sync for shared projects.
Attacks that exploit this kind of access
The rule that runs crow_revoke_access 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_revoke_access, this is the rule to start with:
crow_revoke_access is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_revoke_access call is checked against it from then on.
Questions about crow_revoke_access
Revoke a previously shared item or project from a contact. Stops ongoing sync for shared projects. Returns a preview and confirmation token on first call; pass the token back to execute. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_revoke_access: 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_revoke_access is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the crow_revoke_access 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_revoke_access. 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_revoke_access 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.
Across the catalogue