crow_revoke_instance

Revoke a registered instance — sets status to

SERVERCrow SOURCEkh0pper/crow

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-revoke-instance.md

WHAT IT DOES

What crow_revoke_instance does on Crow

AI agents call crow_revoke_instance 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.

RISK

Why crow_revoke_instance is rated Critical

Revoking an instance removes its ability to function within the system and cannot be easily reversed. While the description is incomplete ('sets status to' is cut off), the semantic meaning of 'revoke' in authentication/authorization contexts is to permanently withdraw access or validity. This is an irreversible action affecting system state.

From the tool's definition Tool name 'crow_revoke_instance' with description 'Revoke a registered instance — sets status to' indicates permanent revocation of an instance registration. Revocation is an irreversible state change that cannot be undone by normal means.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_revoke_instance 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_instance, this is the rule to start with:

crow_revoke_instance Hidden

crow_revoke_instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "crow_revoke_instance"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_revoke_instance call is checked against it from then on.

FAQ

Questions about crow_revoke_instance

What does the crow_revoke_instance tool do? +

Revoke a registered instance — sets status to. 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_instance? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_revoke_instance: 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_instance? +

crow_revoke_instance 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_instance? +

Yes. Add a rate_limit block to the crow_revoke_instance 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_instance completely? +

Set action: deny in the PolicyLayer policy for crow_revoke_instance. 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_instance? +

crow_revoke_instance 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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →