policy_revoke
Revoke an outstanding policy approval immediately. Use when responding to an incident or when a previously approved action is no longer authorized.
This record as markdown: /tools/io-github-ruvnet-claude-flow/policy-revoke.md
What policy_revoke does on Claude Flow
AI agents call policy_revoke to permanently remove resources in Claude Flow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why policy_revoke is rated Critical
This tool irreversibly revokes a policy approval, which is a destructive action that cannot be undone without explicit re-authorization. Unlike a Write operation (which modifies data reversibly), revocation is a one-way state change that removes permissions/approvals. The immediate effect and incident-response framing indicate potential for significant operational disruption if misused.
From the tool's definition The tool 'revokes' an outstanding policy approval 'immediately', and its description explicitly states it is used 'when responding to an incident or when a previously approved action is no longer authorized.' The verb 'revoke' combined with 'immediately' and…
Attacks that exploit this kind of access
The rule that runs policy_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For policy_revoke, this is the rule to start with:
policy_revoke 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 Claude Flow, apply this rule, and every policy_revoke call is checked against it from then on.
Questions about policy_revoke
Revoke an outstanding policy approval immediately. Use when responding to an incident or when a previously approved action is no longer authorized. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Flow MCP server in PolicyLayer and add a rule for policy_revoke: 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 Claude Flow. Nothing to install.
policy_revoke 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 policy_revoke 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 policy_revoke. 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.
policy_revoke is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
Across the catalogue