This record as markdown: /tools/kh0pper-crow/crow-deactivate-server.md
What crow_deactivate_server does on Crow
AI agents call crow_deactivate_server 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_deactivate_server is rated Critical
Deactivating a server disables or shuts down a running service, which can have significant blast radius (all users/services depending on it are affected). This is effectively irreversible in the immediate sense — restoring a deactivated server requires deliberate manual action. It falls under Destructive as it removes operational capability rather than merely modifying configuration.
From the tool's definition "Deactivate a server" — deactivating a server is an irreversible or difficult-to-reverse action that takes a service offline
Attacks that exploit this kind of access
The rule that runs crow_deactivate_server 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_deactivate_server, this is the rule to start with:
crow_deactivate_server 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_deactivate_server call is checked against it from then on.
Questions about crow_deactivate_server
Deactivate a server. 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_deactivate_server: 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_deactivate_server 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_deactivate_server 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_deactivate_server. 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_deactivate_server 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