maker_revoke_batch
Revoke every session in a batch (use when a printed QR sheet is lost). Admin-only. Requires a reason (logged).
This record as markdown: /tools/kh0pper-crow/maker-revoke-batch.md
What maker_revoke_batch does on Crow
AI agents call maker_revoke_batch 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 maker_revoke_batch is rated Critical
Revoking sessions is a destructive action—it irreversibly terminates active user sessions and cannot be reversed without user re-authentication. While admin-restricted and logged, a compromised admin account or misconfiguration could mass-revoke legitimate sessions, causing significant service disruption and denial of access.
From the tool's definition Tool name 'maker_revoke_batch' combined with description 'Revoke every session in a batch' indicates irreversible termination of multiple active sessions.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs maker_revoke_batch 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 maker_revoke_batch, this is the rule to start with:
maker_revoke_batch 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 maker_revoke_batch call is checked against it from then on.
Questions about maker_revoke_batch
Revoke every session in a batch (use when a printed QR sheet is lost). Admin-only. Requires a reason (logged). 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 maker_revoke_batch: 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.
maker_revoke_batch 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 maker_revoke_batch 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 maker_revoke_batch. 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.
maker_revoke_batch 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