Critical Risk →

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.

How to control crow_revoke_access ↓

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.

Critical Risk

Why crow_revoke_access needs a policy

Revoking access and stopping ongoing sync is an irreversible action that removes a contact's access to shared items/projects. While a confirmation token mechanism exists, the action itself — terminating sharing relationships and sync — cannot be easily undone and constitutes a destructive operation with potentially high blast radius if misused against legitimate collaborators.

From the tool's definition Revoke a previously shared item or project from a contact. Stops ongoing sync for shared projects.

Documented attack patterns abuse exactly the kind of access crow_revoke_access gives an agent:

How to control crow_revoke_access

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_revoke_access:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "crow_revoke_access"
  ]
}

crow_revoke_access disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_revoke_access

What does the crow_revoke_access tool do? +

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.

How do I enforce a policy on crow_revoke_access? +

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.

What risk level is crow_revoke_access? +

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.

Can I rate-limit crow_revoke_access? +

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.

How do I block crow_revoke_access completely? +

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.

What MCP server provides crow_revoke_access? +

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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.